[buildd-tools-devel] Bug#608972: Bug#608972: Bug#608972: sbuild: How does that “local apt archive” work?
Roger Leigh
rleigh at codelibre.net
Mon Feb 14 20:40:32 UTC 2011
tags 608972 + fixed-upstream pending
thanks
On Wed, Jan 05, 2011 at 05:37:08PM +0100, Cyril Brulebois wrote:
> Roger Leigh <rleigh at codelibre.net> (05/01/2011):
> > The apt archive is an internal implementation detail of the apt and
> > aptitude resolvers. It hasn't been documented because it is
> > indended to be entirely transparent to the user; it only exists
> > transiently during the package build and there is nothing user-
> > configurable about it. It does not persist across builds, and it is
> > only used to store the dummy dependency packages for a single build.
>
> Still, “local apt archive” is mentioned. One may think it's related to
> having ones own packages added to the standard pool, for example
> because one doesn't want to wait a package to be installed in the
> archive before building another one build-depending on it. So that's
> confusing, and that's why I asked.
The description of how the local archive works is now documented in
sbuild.1; please let me know if it needs any further improvement.
Thanks,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20110214/a02129d4/attachment.pgp>
More information about the Buildd-tools-devel
mailing list