[debiancolombia] Empaquetango un egg de Chicken

[Santiago Ruano Rincón]

Hola Nelson,

On Sat, Sep 15, 2007 at 08:46:00PM -0500, Nelson Castillo wrote:
...
> 
> Hola.
> 
> Como conté antes, los desarrolladores
> de Chicken prefieren tener toda la información de
> los eggs dentro de los eggs, y no creo que cambien de
> idea. Cuando conté que podía separar los archivos, como
> que no le pareció la idea y no creo que cambien de opinión
> fácil :)
> 
> Si bien no es lo más deseable desde el punto de vista de
> los desarrolladores de Debian, ¿Esto sería un problema?
> 
>   Esto me respondieron:
> 
>   What is the purpose of creating these files? If you just
>   run dpkg-buildpackage in an egg directory that contains
>   subdirectory debian/ with the required Debian scripts in it,
>   the tool will create the binary and source packages. I prefer
>   to keep the debian directory in the eggs repository, so that it
>   is easier to track changes to the eggs.  I am naming the
>   packages chicken-egg-name, so for example srfi-40 is
>   chicken-srfi-40 -- this is analogous to the Common Lisp
>   packages that are present in Debian.
> 

Copio y pego la razón de "The debian-mentors FAQ" [1]:

	"What's wrong with upstream shipping a debian/ directory?

	There are cases where upstream ships a tarball which already contains a
	debian directory. This is undesirable, even if you're upstream yourself
	or can commit there. Keep the released tarballs (used as .orig.tar.gz)
	and the debian directory separated.

	The problem is that at some point, upstream's debian directory will
	deviate from the one in the Debian package -- because the maintainer
	changes, the directory was already outdated, or someone does an NMU or a
	security upload. Because it was The .diff.gz will now be a diff between
	the two debian dirs, which is very confusing.

	The Debian package format is designed to keep upstream and
	Debian-specific neatly separated into orig.tar.gz and .diff.gz. Putting
	the debian dir in the .orig.tar.gz confuses this.

	If upstream has a debian directory in their releases, you should contact
	them and ask if they can remove the debian/ directory from their tarball
	releases. There's no need to remove the debian directory from their
	revision control system (although if it's out of date they may decide to
	do so anyway), but at the very least the directory shouldn't appear in
	releases. If you are upstream yourself, well, you can ask yourself to do
	it." 

[1] http://people.debian.org/~mpalmer/debian-mentors_FAQ.html

> Por cierto, este es el hilo. Todavía no se ve el mensaje
> que acabo de mostrar.
> 
> http://www.mail-archive.com/chicken-hackers@nongnu.org/msg00350.html
> 
> Por cierto, el proceso de empaquetado va bien. Ivan ha estado
> integrando su trabajo con paquetes de Debian a la versión oficial,
> y voy a ayudar creando más paquetes para terminar con las
> dependencias de Svnwiki. Svnwiki usa autoconf/automake, y que
> espero que eso me facilite el creado del paquete del programa.
> 
> Atte,
> Nelson.-
> 
> -- 
> http://arhuaco.org

Saludos,

Santiago
------------ próxima parte ------------
Se ha borrado un mensaje que no está en formato texto plano...
Nombre     : no disponible
Tipo       : application/pgp-signature
Tamaño     : 189 bytes
Descripción: Digital signature
Url        : http://listas.debiancolombia.org/pipermail/general/attachments/20070915/9a5e088f/attachment.pgp