2 ms·
the memory in my s/w development history was a long-lived build host which had masses of install-loop dependencies (things which need earlier versions of themse
by ggm 3y ago
the memory in my s/w development history was a long-lived build host which had masses of install-loop dependencies (things which need earlier versions of themselves to exist, to bootstrap installing the one you want) as well as dependencies hidden inside things. Basically, "it built on <x>" became a stock joke because it was demonstrably true: anything would build on a host with almost all dependencies resolved, if badly.
one thing containers do is provide an audit/reproducible basis to say WHY something builds. it may still be an implicit dependency: something in a specific version of an underlying substrate like the OS or a boot time act which works on that container and not on another. You may not "see" it at first but its a lower bar to understanding it, if the revision control behind the build chain is good enough.
a build chain of :latest is probably not good. reproducible builds drive against that.
I don't build things for a living any more. Probably this is all well known and argued better by others.