Hello friends!

Before anyone wastes their time on this: I�m preparing a
dpkg_1.4.1.4_i586-pc-gnu.tar.gz package for you. It should
be ready later today (gimme a few hours). It is already compiled,
and i only need to do some testing and package it together manually
(the build process breaks badly on the scripts dpkg-gencontrol and
dpkg-parsechangelog).

For your information, a mixture of impressions, experiences etc.

* I used the gnu-0.2 binary distribution for a native compile.
  Cross compiling won�t even configure (because configure needs
  to compile and start programs for int size). I tried to hack it
  for a cross compile, but failed.

* I used dpkg-1.4.1.4 from klee�s home directory on master.
  It is ready for porting, whereas the latest dpkg in slink
  some kernel headers uses (for sysinfo). This won�t work on Hurd,
  naturally.

* I needed to change PATH_MAX in dpkg/help.c to some value.
  I randomly picked 2048 (hope it�s big enough for now).

* Biggest problem: dpkg --print-architecture. I tried to hack it
  but gave up. Someone else has to change lib/arch.c to support
  GNU archhitecture.

* The build process in detail (for those interested):
  (unpacking dpkg-1.4.1.4.tar.gz, renaming directory, entering)
  debian/rules build  # this starts to do some things, and then
                      # fails trying to execute debian/build/configure
  cd debian/build
  make
  # now hopefully all things compile. There is a problem with
  # the emacs elc generation, where segfaults etc happen.
  # Hurd hung more than one time :) Maybe it�s just the nsswitch
  # thing, have to try again later.
  make binary
  # This will create $(source_tree)/debian/build/debian/tmp
  # where the individual packages are put in place.
  # make binary aborts when dpkg-gencontrol tries to get architecture
  # see above. But most things already happened (for example,
  # libtool did its work etc).

  Now I only need to gather things together for a tar package.
  This is my planned procedure:

  * Make dpkg tar package, which contains all things that are in
    the normal deb.
  * Make a support package which contains a first /var/lib/dpkg
    tree with first entries.
  * Either make further tar packages with dpkg-dev or even
    provide them in dpkg format. have to try.

Now to the technical part: When I have the packages ready,
I�ll upload them to my home directory on master, unless somebody
points me to a ftp site where I can uplaod them (the ftp site
should have a good connection to germany). I�ll only upload them
once. Someone else has to copy/mirror them.

Have fun!

Marcus

PS: Gord, I hope this mail isn�t too verbose for you :)

-- 
"Rhubarb is no Egyptian god."        Debian GNU/Linux        finger brinkmd@ 
Marcus Brinkmann                   http://www.debian.org    master.debian.org
[EMAIL PROTECTED]                        for public  PGP Key
http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/       PGP Key ID 36E7CD09


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to