Developers/Fedora/lang-es: Difference between revisions

From OLPC
Jump to navigation Jump to search
(Arreglar el menu de navegación)
Line 8: Line 8:
== Terminología ==
== Terminología ==


;autores previos
;upstream authors
: 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
: are people who release source code for consumption by '''package maintainers''' and who accept or reject patches from interested individuals


;mantenedores de paquetes
;package maintainers
: are people who accept source code releases from '''upstream authors''' and who combine that source code with '''packaging instructions''' in order to produce '''packaged software'''
: 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
: 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.''
: ''Frequently in OLPC, package maintainers and upstream authors are the same person.''


;lanzamientos de fuentes
;source releases
: 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.
: 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.)
: (it's important for many reasons that source code be ''permanently'' accessible for all packages. ''Please'' make sure that yours is.)


;empaquetando instrucciones
;packaging instructions
: consist of a '.spec' file and zero or more patches to a source release.
: consiste en un archvio '.spec' y zero o mas parches al lanzamiento de fuentes.


;empaquetando codigo fuente
;packaged source code
: is the 'source object' of a software distribution much as '.c' and '.h' files are the units of source code for building C binary objects.
: 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.


;packaged software
;empaquetando software
: is the 'binary object' of a software distribution much as '.o' files are the binary objects linked together to produce C binaries
: 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 ==
== Lectura externa ==

Revision as of 07:15, 31 May 2011

Previo Regresar al indice

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

Here is a collection of sites that I have found useful in learning to maintain Fedora packages for OLPC:

Procedimientos de Fedora

Tips de RPM

Creando o modificando RPMS

Infraestructura Fedora

Previo Regresar al indice