<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Am 06.11.24 um 14:30 schrieb Rob C. via
oi-dev:<br>
</div>
<blockquote type="cite"
cite="mid:OFB571E66A.F9ED8ACF-ON85258BCD.00482A7C-85258BCD.004A34F3@atto.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<span style=" font-size:10pt;font-family:sans-serif">Just doing "</span><span
style=" font-size:12pt">pkg install build-essential", I get the
incorporation error:</span><br>
<br>
<span style=" font-size:12pt">pkg install: No matching version of
metapackages/build-essential can be installed:</span><br>
<span style=" font-size:12pt">Reject: <a
class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:pkg://openindiana.org/metapackages/build-essential@15-2024.0.0.0">pkg://openindiana.org/metapackages/build-essential@15-2024.0.0.0</a></span><br>
<span style=" font-size:12pt">Reason: This version is excluded by
installed incorporation <a
class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:consolidation/userland/userland-incorporation@0.5.11-2022.0.0.17367">consolidation/userland/userland-incorporation@0.5.11-2022.0.0.17367</a></span><br>
<br>
<span style=" font-size:10pt;font-family:sans-serif">The pkg
update allows build-essential to install but it also upgrades
the kernel to 2024. I need to support an older kernel.</span><br>
<br>
</blockquote>
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.<br>
First, OI uses the meta packages userland-incorporation and
osnet-incorporation to create baselines that fixate most packages of
the system.<br>
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...<br>
<br>
Second, we have a rolling release model. That is, we don't have real
releases which we support.<br>
<br>
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.<br>
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.<br>
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.<br>
This is the reason you cannot download additional packages in an old
boot environment after a shrink has be done anymore.<br>
Can the situation enhanced? Probably, but not with the actual
resources we have.<br>
<br>
Andreas<br>
</body>
</html>