Hi Peter,
Peter Polidoro writes:
> For every commit to the Guix master branch, is there a guarantee that
> there are no packages with broken dependencies?
There's no strong guarantee; we rely on people having well tested their
changes and reviewing what QA had to say about it. Any unexpected
If a borked dependency will be uploaded, every build that depends on such a
dependency will change hash, and therefore will have to be rebuilt. The build
process also includes testing.
Since all updates are atomic, if any one package fails nothing gets updated, and
you can continue using your
For every commit to the Guix master branch, is there a guarantee that there are
no packages with broken dependencies?
I have not experienced packages with broken dependencies, so I am curious how
that is checked. In theory, someone could make a commit that accidentally
breaks other packages
