On 22/09/2026 17:58, Peter Tribble wrote:
On Sat, Sep 19, 2026 at 12:56 AM Reginald Beardsley via
openindiana-discuss <[email protected]> wrote:
The significant issue is that such a trivially identifiable fault should make
it to publication in an OI repository. That should not happen.
My concern is preventing such things from happening by automating verification
the packages link. Back in the day one job required that my install packages
worked flawlessly. They always did. This is not hard work and I am willing to
do it, though I need to get on the oi-dev list again to discuss that.
So the problem is not that broken new packages are published
A package repository has to be considered a single entity, a set of
packages. If a package breaks others then it is broken. The "it" being
the repository. Interdependent package releases should be done atomically.
The Blastwave the stable release was made by assembling a set of release
candidate packages (basically a snapshot of unstable but with selected
packages removed) and testing them, including ldd checks as Reg suggests.
The OI model of a single rolling release does not lend itself to such
scrutiny.
The Image Packaging System allows multiple versions in one repository
and can only be considered a single entity using the latest versions for
any given time. It is still possible to freeze and archive by creating
new repositories.
_______________________________________________
openindiana-discuss mailing list
[email protected]
https://openindiana.org/mailman/listinfo/openindiana-discuss
