❦ 14 mai 2015 14:57 +0100, Neil Williams <[email protected]> : >> More seriously, but this needs some additional work, it should be >> easier to manage persistent build dependencies. The first time you >> build a package, it retrieves and install all deps. The second time, >> the build environment is already here. > > That's a (serious) bug, not a feature. > > Either you want clean build environments or you are prepared to build > in dirty ones, in which case there's little point using a container at > all. > > A package cache is different, that's what pbuilder uses - that avoids > the risk of stale packages being installed, not being updated and > breaking the build. Either do it by uninstalling at the end of the > build or by using a disposable container (LVM snapshot or pbuilder > chroot). At all costs, avoid the false appeal of a dirty container > which gets you none of the advantages and all of the problems of > building on a developer box with no container at all. > > Were you thinking of a package cache or a dirty container? > > Any build system which allows for dependencies of a previous build to > exist at the start of the next build is irretrievably broken and unfit > for purpose. All you can allow to exist at the start of the build is > build-essential.
For some packages, installing the dependencies can take more time than
building the package. This makes use of pbuilder/cowbuilder quite
tiresome. If the whole dependencies are already here, this becomes more
enjoyable.
This is not a dirty container. Only the dependencies needed for the
packages are retrieved. If the build environment for the package doesn't
exist, a new environment is created. Old environments are removed after
a day. Something like that.
--
Sometimes I wonder if I'm in my right mind. Then it passes off and I'm
as intelligent as ever.
-- Samuel Beckett, "Endgame"
signature.asc
Description: PGP signature
