[prev in list] [next in list] [prev in thread] [next in thread] 

List:       illumos-developer
Subject:    [developer] [RFC] Ship closed-binaries in-tree and deliver them as part of the build
From:       Richard Lowe <richlowe () richlowe ! net>
Date:       2024-04-30 20:48:30
Message-ID: CAA7J0x_5GxaOEGGnq_=fuapnibiQJEBF7D9LuK+6a11i7CPyfg () mail ! gmail ! com
[Download RAW message or body]

https://code.illumos.org/c/illumos-gate/+/3445

This makes reasoning (which binaries do we use?) much easier, it also would
allow us in the future to deliver them to _different places_, should we want
to stop isaexec'ing iked, move pax to usr/has, or rearrange drivers into
/platform or /usr/kernel.

It also makes the delivery of licenses via the closed-bins (seriously,
they drop into the proto out of there) less likely to cause us to
accidentally use an older license if the build races (this  can be
fixed with the exception list, too, but as an example of what the
greater visibility brings out)

I intend this as a basis for discussion, and I think that's best done
by showing you the code and letting you look at a version that
actually works to see how this would look.  If we want to pursue this
route, I would write up an IPD that is basically a copy/paste of the
above, and a summary of the outcome of the discussion.

The makefiles are intentionally lacking framework and modularity, as
the nature of the task means that changes to them are even in the best
case, very unlikely, and they are few.

-- Rich

------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/Tb64944d83604d344-=
M27ba9d393d6dd856fea170a0
Delivery options: https://illumos.topicbox.com/groups/developer/subscription
[prev in list] [next in list] [prev in thread] [next in thread]