If you want to test the latest bleeding-edge source code for aptitude, you can download unreleased aptitude source code using Git. Install Git (available from http://git-scm.com/) and execute the command git clone git://git.debian.org/git/aptitude/aptitude.git to retrieve the most recent source code.
![]() | Aviso |
---|---|
The aptitude Git repository is an active development tree; it will change as bugs are fixed and features are added, and there is absolutely no guarantee that it will even compile, let alone run properly! Bug reports are welcome, but be aware that you use development code entirely at your own risk![1] |
La lista de correo principal para aptitude es
<aptitude-devel@lists.alioth.debian.org>
. Los archivos de esta
lista se encuentra en http://lists.alioth.debian.org/pipermail/aptitude-devel/. Para
suscribirse, visite la página web http://lists.alioth.debian.org/mailman/listinfo/aptitude-devel.
Preferentemente, los parches se han de enviar a la lista de correo de
aptitude <aptitude-devel@lists.alioth.debian.org>
. Pero si
prefiere mandarlos a través de un correo privado, debe hacerlo a
<aptitude@packages.debian.org>
o a
<dburrows@debian.org>
. Apreciaríamos de manera especial una
breve descripción de la motivación que hay detrás de su parche, y una
explicación de su funcionamiento.
The aptitude source tree is regularly updated with new features, bugfixes, and new bugs. Once the source code is available on your computer (see the previous section), you can cd into it and type git pull to update it with any changes made to the main repository.
To automatically receive notifications when changes are made to the aptitude codebase, subscribe to the Atom feed available at http://anonscm.debian.org/gitweb/?p=aptitude/aptitude.git;a=atom or RSS feed available at http://anonscm.debian.org/gitweb/?p=aptitude/aptitude.git;a=rss.
To build aptitude from the Git repository, you must have the programs
autoconf
and automake
installed. Type sh ./autogen.sh && ./configure
to generate the files needed to compile aptitude, then execute
make and make install.
[1] Por supuesto, todo el software libre se emplea bajo la responsabilidad del usuario, pero el riesgo relacionado con usar un árbol de desarrollo activo es mucho mayor.