Re: Modern Debian packaging system for DevOps: does it exist?
]] Neil Williams
> > This is not a dirty container.
>
> Sorry, it is dirty. It just is. It's dirty in the worst possible manner
> - stuff directly relating to the builds you care about is going to end
> up out of date or possibly even corrupted by a mis-configured build.
> There's nothing "modern" about debugging issues arising from dirty
> containers, it's completely unnecessary and a false economy.
It's no more dirty than a prebuilt tarball or chroot with just required
+ build-essential. It's not like those never change.
> A container where the dependencies remain installed is a dirty
> container. What happens when there is a transition in one and someone
> forgets to update the dependencies to save time?
Then you have a buggy design. In such a design you would want to have a
list of correct versions to have installed and any mismatches gets fixed
automatically.
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
Reply to: