[5859] in Release_7.7_team
Re: Proposed repository plan for Athena 10 work
daemon@ATHENA.MIT.EDU (Aaron M. Ucko)
Wed Oct 10 11:41:14 2007
To: Greg Hudson <ghudson@MIT.EDU>
Cc: release-team@MIT.EDU
From: amu@alum.MIT.EDU (Aaron M. Ucko)
Date: Wed, 10 Oct 2007 11:40:36 -0400
In-Reply-To: <Release_7.7_team:5858@unknown-discuss-server> (Greg Hudson's message of "Wed, 10 Oct 2007 00:39:06 -0400")
Message-ID: <udl7ilvq8p7.fsf@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Flag: NO
X-Spam-Score: 0.00
Greg Hudson <ghudson@MIT.EDU> writes:
> Details may change as I learn more about how dpkg works.
In general, all you actually need to build binary packages is a
suitably prepared source tree, with a debian directory containing
files related to building the package (most crucially, changelog,
control, and rules); you can either patch upstream code directly or
stash patches under debian/ and arrange for debian/rules to apply them
at build time.
Pristine upstream sources (preferably pre-tarred, but see
http://kitenet.net/~joey/code/pristine-tar/) mainly come into play
when (additionally) building source packages, though it is of course
good practice to do so. (Debian's build infrastructure will generate
the .diff.gz for you.)
You may also find Debian's New Maintainers' Guide
<http://www.debian.org/doc/maint-guide/> to be of interest.
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?amu@monk.mit.edu
