Bug#200654: ITP: debpool -- pool-based DEB package archiver
On Wed, 2003-07-09 at 14:55, Joel Baker wrote:
> DebPool is a pool-based DEB
s/DEB/Debian/ ?
> package archiver designed with a goal of
> removing any dependancy on code not shipped as part of the core Debian
> system.
By "core" here do you mean priority >= standard?
> It is capable of all of the following:
> * Tracking multiple distributions (however, it does *not* include
> unstable -> testing promotion scripts).
> * Generating Release files (requires libdigest-{md5,sha1}-perl)
> * Verifying package signatures (requires gnupg).
> * Signing release files (requires Release files and gnupg).
> * Running in single-pass or daemon modes.
>
> DebPool is intended to be a lightweight replacement for the full Debian
> archival scripts, in the tradition of debarchive and mini-dinstall, but
> using a pool layout
How are you implementing this? Do you have some sort of database about
which packages are in which distributions?
> and avoiding external dependancies.
This seems like an unfortunate reason to write a whole new program. If
the problem is mini-dinstall's dependency on python-logging, I could
probably suck it into the package. In any case it'll be standard in
Python 2.3 which is why I've been lazy about doing it.
Reply to: