Re: [rms@santafe.edu: Hurd packager]
- To: Jim Pick <jim@jimpick.com>
- Cc: debian-hurd@kato.legislate.com, Ean Schuessler <ean@novare.net>, debian-devel@lists.debian.org, rms@gnu.org
- Subject: Re: [rms@santafe.edu: Hurd packager]
- From: Raul Miller <rdm@test.legislate.com>
- Date: Sun, 28 Jun 1998 11:16:51 -0400
- Message-id: <[🔎] 19980628111651.C10599@test.legislate.com>
- Mail-followup-to: Jim Pick <jim@jimpick.com>, debian-hurd@kato.legislate.com, Ean Schuessler <ean@novare.net>, debian-devel@lists.debian.org, rms@gnu.org
- In-reply-to: <[🔎] 87emwamp6m.fsf@fleming.jimpick.com>; from Jim Pick on Sat, Jun 27, 1998 at 03:53:53PM -0700
- References: <[🔎] 19980626154309.G7391@novare.net> <[🔎] 19980626200334.F9094@test.legislate.com> <[🔎] 87emwamp6m.fsf@fleming.jimpick.com>
Jim Pick <jim@jimpick.com> wrote:
> It doesn't look like it would be too hard to get dpkg going on it.
> Most of the other GNU tools are already there.
To get dpkg going, you need perl5.004, gettext, autoconf and automake.
[you'd need more if you were going to get dselect and the documentation
to build, but you don't need that right away.]
Once you have dpkg built, and its executables installed, it's pretty
simple to pull down the base packages (everything on ftp.debian.org
or one of its mirrors for pub/debian/dists/hamm/main/source/base/).
The easy part is:
for x in *dsc; do dpkg-source -x $x; done
for d in */; do (cd $d; chmod +x debian/rules; nohup debian/rules build) done
[then you fix any problems that prevented you from building everything.]
The easy way of building the packages is
for d in */; do (cd $d; nohup debian/rules binary) done
If I recall correctly, there's a package around to build the base disks
from these packages, but I'm still not sure if that's a problem that
needs to be solved.
--
Raul
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: