On Wed, 1 Aug 2007, Danek Duvall wrote:
> On Wed, Aug 01, 2007 at 04:13:57PM -0500, Eric Boutilier wrote:
>
>> Anyway, in light of this, my take now is that coming up with the 100%
>> open-source thing from which the distro constructor will build is
>> actually going to be rather tricky business, correct? If so, can I and
>> others interested in this concept help in any way at this point?
>
> Well, to be fair, the bulk of the packages that don't come from ON or SFW
> are from NWS, and are there so people can boot off of fibrechannel SAN
> devices and fun things like that. I don't know if those really need to be
> in Indiana, at least for the first cut.
>
> After that, you've got devpro things like libC, libm, and cpp. JES brings
> in NSS and NSPR. Install gives you the packaging and patching utils and
> prodreg. And all of this stuff is opensource now, isn't it?
>
> I can provide the complete lists, if you like, though anyone can generate
> it from an install image's .clustertoc and a list of ON packages.
The thing that I'm calling tricky, but that might be very useful at
this point I think, would be to identify and tabulate encumberances in
terms of our existing smallest supportable core, SUNWCrnet:
Step 1. Identify packages in SUNWCrnet that are vital (from the perspective
of the constructor kit) but currently non redistributable.
Step 2. Building on set #1, expand to include the non-redistributable
packages that are important (as opposed to vital).
Then repeat 1 and 2 substituting non open-source for non redistributable.
Eric
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
