[oi-dev] How to get build-essential for older OS release.

[Andreas Wacknitz]

Am 06.11.24 um 14:30 schrieb Rob C. via oi-dev:
> Just doing  "pkg install build-essential", I get the incorporation error:
>
> pkg install: No matching version of metapackages/build-essential can
> be installed:
> Reject: pkg://openindiana.org/metapackages/build-essential@15-2024.0.0.0
> Reason:  This version is excluded by installed incorporation
> consolidation/userland/userland-incorporation at 0.5.11-2022.0.0.17367
>
> The pkg update allows build-essential to install but it also upgrades
> the kernel to 2024. I need to support an older kernel.
>
Why do you want that? If you need to support systems with old boot
environments (that is, systems that haven't been updated for a while)
then OI in its momentary way of development is not sufficient for you.
First, OI uses the meta packages userland-incorporation and
osnet-incorporation to create baselines that fixate most packages of the
system.
This is intended because it allows for a combination of packages that
are intended to work together (I would like to omit the "intended" but I
cannot because the reality is that we don't have the resources for it).
So, you cannot mix package versions from different baselines. When you
uninstall these two packages (and the package entire) you are free to
mix versions but the result may not working as expected. So if you
uninstall these packages you should really know what you are doing...

Second, we have a rolling release model. That is, we don't have real
releases which we support.

Theretically it would be possible to provide what you are asking for.
That is, to keep all package revisions for a long period. Alas this is
not practical for some reasons.
First, we have storage limitations. But that is only a minor problem.
The bigger problems were created by the sheer amount of data that has to
be processed during updates.
So in order to keep the time and memory requirements for package
management in a managable region we need to shrink the repositories from
time to time by just keeping the latestet package revisions.
This is the reason you cannot download additional packages in an old
boot environment after a shrink has be done anymore.
Can the situation enhanced? Probably, but not with the actual resources
we have.

Andreas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20241106/1dc17f57/attachment.html>