On Wed, Aug 20, 2003 at 09:52:08AM +0200, Marc Haber wrote:
> On Wed, Aug 13, 2003 at 01:37:00PM +0100, James Troup wrote:
> > Martin Michlmayr <tbm@cyrius.com> writes:
> > > * Marc Haber <mh+debian-packages@zugschlus.de> [2003-08-13 07:58]:
> > >> > I'm glad that we have so much manpower that we can use it on endlessly
> > >> > reinventing this wheel.
> > >>
> > >> Please point me to the other instances of this wheel.
> > >
> > > Package: mini-dinstall
> >
> > And debpool (#200654)
>
> This is not yet in the archive, and not even published. A bad case of
> duplicated effort indeed, but the main work related to
> package-pool-helper is already done.
Though I'd call debpool 90% done. I got distracted from finishing it by
NetBSD license stuff suddenly becoming active again; what remains is
touch-ups rather than crucial pieces.
> Joel, may I ask to see a preliminary version of your package to see if
> your package can do what package-pool-helper can do and whether "my"
> functionality can be added to "your" package?
Certainly. I just ran dpkg-source over the existing setup; you can grab it
at:
http://users.lightbearer.com/lucifer/debian/debpool_0.1.0.{dsc,tar.gz}
Note that this is in the exact state of my working space at the moment, so
it isn't guaranteed to actually be a clean package (all the code should be
clean, but I don't remember if I finished debian/rules, and the TODO file
lists things remaining).
The two big things that I can think might matter (apart from, of course,
handling pools) are the ability to generate Release files, and to use GnuPG
to verify signed changes/dsc files, or sign Release files. (Verification
of actual in-package signatures by debsig-verify doesn't work yet; it's an
eventual goal, but not for the first release).
> > and debarchiver
>
> Doesn't seem to handle package pools.
It doesn't, nor is it easy to patch, or I'd never have started debpool. :)
> > and nihkatienumber345, etc. ad nauseam.
>
> How very helpful of you.
>
> Fact is that whenever I mention my package pool scripts in a lecture
> or in a developer's meeting, I keep getting requests for the scripts
> "since there is nothing like that in Debian yet". Either the existing
> packages are hard to find, or they are missing some features (maybe
> non-dependency on python, or simplicity) that my scripts have.
>
> Experience says that the fact that the file controlling "package foo
> goes into distribution bar" is in the very same directory with the foo
> package files makes pool management extremely easy.
Hmmmm. Debpool manages version information by using tied hashes, and puts
the changes files into an 'installed' directory; perhaps this should
be reconsidered. In any case, look at the code; it sounds like the two
packages might actually (unlike debarchiver or mini-dinstall) be close
enough to overlap significantly, and possibly be merged.
Followup should probably should drop all the other Cc's on it, unless any
of them are crucially interest int he details for some reason. :)
--
Joel Baker <fenton@debian.org> ,''`.
Debian GNU NetBSD/i386 porter : :' :
`. `'
`-
Attachment:
pgpIGGz70eTZI.pgp
Description: PGP signature