Developers/Fedora/lang-es: Difference between revisions
< Developers | Fedora
Jump to navigation
Jump to search
Line 41: | Line 41: | ||
=== Tips de RPM === |
=== Tips de RPM === |
||
* http://fedoranews.org/alex/tutorial/rpm/ '' |
* http://fedoranews.org/alex/tutorial/rpm/ ''Paseo por las tareas comunes relacionadas con RPM'' |
||
=== Creando o modificando RPMS === |
=== Creando o modificando RPMS === |
Revision as of 07:22, 31 May 2011
For Developers
Introducción
OLPC maintains a variant of the Fedora Linux distribution. Many developers, over the course of their careers developing for the XO, develop a need to package software for the XO, either because they wish to fix a bug in software contained in an existing package or because they wish to contribute new software (other than activities) to the system. We do this through packaging the software in the upstream Fedora community, a process which this page aims to introduce.
Terminología
- autores previos
- son las personas que liberan las fuentes de codigo para el consumo del mantenedor de paquetes y quien acepta o rechaza los parches por individuos interezados
- mantenedores de paquetes
- are people who accept source code releases from upstream authors and who combine that source code with packaging instructions in order to produce software empaquetados
- package maintainers are also responsible for contributing patches to upstream authors that fix bugs or that make the upstream software inter-operate more smoothly with other software
- Frequently in OLPC, package maintainers and upstream authors are the same person.
- lanzamientos de fuentes
- are typically tarballs of source code that have been permanently published at a fixed URL, along with validation data such as MD5sums or the author's public key and a digital signature.
- (it's important for many reasons that source code be permanently accessible for all packages. Please make sure that yours is.)
- empaquetando instrucciones
- consiste en un archvio '.spec' y zero o mas parches al lanzamiento de fuentes.
- empaquetando codigo fuente
- es el 'objeto fuente' de las distribuciones de software de forma que los archivos '.c' y '.h' son las unidades de codigo fuente para construir objetos binarios en C.
- empaquetando software
- es el 'objeto binario' de una distribuci[on de software muy similar a archivos '.o' son objetos binarios ligados entre ellos para producir un binario C
Lectura externa
Aqui una coleccion de vinculos que me han ayudado a aprender el mantenimiento de paquetes Fedora para OLPC:
Procedimientos de Fedora
- http://fedoraproject.org/wiki/Join_the_package_collection_maintainers - Únete a los mantenedores de paquetes
- https://fedoraproject.org/wiki/PackageMaintainers/UpdatingPackageHowTo - Como actualizar los paquetes mantenidos en Fedora
- https://fedoraproject.org/wiki/PackageMaintainers/UsingCvsFaq - Como acceder el código fuente para paquetes mantenidos en Fedora
- http://fedoraproject.org/wiki/PackageMaintainers/UsingKoji - Como construir un RPM con la infraestructura construida con Fedora
- http://fedoraproject.org/wiki/Packaging/ReviewGuidelines - Lista de chequeo que debe ser confirmada para agregar nuevos paquetes a Fedora
Tips de RPM
- http://fedoranews.org/alex/tutorial/rpm/ Paseo por las tareas comunes relacionadas con RPM
Creando o modificando RPMS
- http://docs.fedoraproject.org/drafts/rpm-guide-en/ch-creating-rpms.html - Draft reference material on how to create RPMs
- http://rpm.org/max-rpm-snapshot/ - Out of date reference material on how to create RPMS
- http://fedoraproject.org/wiki/Docs/Drafts/BuildingPackagesGuide - Recent but incomplete walk-through of how to create Fedora packages
Infraestructura Fedora
- https://admin.fedoraproject.org/pkgdb/ - Website for managing authorization to update Fedora packages
- http://koji.fedoraproject.org/koji/ - Status website for the Fedora build system