public inbox for developer@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
From: Gordon Ross <gordon.w.ross@gmail.com>
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] [RFC] Ship closed-binaries in-tree and deliver them as part of the build
Date: Wed, 1 May 2024 14:24:55 -0400	[thread overview]
Message-ID: <CAD0Ztp3RLW-wynJWRtitDQm_uURYbLUyv7jpgxD4JmQRtak5Dw@mail.gmail.com> (raw)
In-Reply-To: <CAA7J0x_5GxaOEGGnq_=fuapnibiQJEBF7D9LuK+6a11i7CPyfg@mail.gmail.com>

Looks like a potentially useful improvement.
What's the impact on the size of a "git clone"?

On Tue, Apr 30, 2024 at 4:49 PM Richard Lowe <richlowe@richlowe.net> wrote:
>
> 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

  reply	other threads:[~2024-05-01 18:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30 20:48 Richard Lowe
2024-05-01 18:24 ` Gordon Ross [this message]
2024-05-01 19:56   ` [developer] " Richard Lowe
2024-05-01 18:33 ` Peter Tribble
2024-05-01 19:55   ` Richard Lowe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAD0Ztp3RLW-wynJWRtitDQm_uURYbLUyv7jpgxD4JmQRtak5Dw@mail.gmail.com \
    --to=gordon.w.ross@gmail.com \
    --cc=developer@lists.illumos.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).