[oi-dev] pkg.openindiana.org/experimental updated - now with gcc-44

Jim Klimov jimklimov at cos.ru
Sun May 6 16:06:51 UTC 2012


2012-05-06 17:48, Alasdair Lumsden wrote:
> Once /stable comes out this won't be a problem as things will logically fork.


On a side note, do we have an intuitive way of installing
a certain release of OpenIndiana (i.e. for reproducibility
of problematic or otherwise interesting setups, or for
organizations who certify a particular software image as
"known-good" for their environment)?

I thought of package repository paths like "/stable/oi148"
or "/stable/oi151a3" pointing to software at time of release
(same as LiveCD for basic packages), and possibly including
sub-sub-sub-versions for minor updates.

A user seeking to update would change desired repo to a new
"stable/oiXXX" or perhaps "stable/oiXXXuU" for maintenance
update releases, and run pkg image-update.

At the very least, are all of the released package versions
available in the common repo, so filters can be used to
extract particular release versions?

Thanks,
//Jim




More information about the oi-dev mailing list