On May 11, 2013, at 6:01 PM, Theo Schlossnagle <[email protected]> wrote:
> On Sat, May 11, 2013 at 10:59 AM, Garrett D'Amore <[email protected]> wrote: > I think OmniOS is almost there -- the "problem" is that OmniOS has made some > changes (IMO good ones) that illumos has not -- specifically nixing a bunch > of the broken or ancient printing infrastructure. With these changes, it is > not possible to compile stock illumos on OmniOS (or at least it wasn't the > last time I tried). > > IMO, the best solution for us is to adopt the same change in illumos -- but > this gets into another rat hole discussion -- because some people apparently > *like* those crappy crufty printing tools. I'm strongly of the opinion that > we ought to just go ahead in spite of those complaints, as the source for the > SystemV printing stuff will always remain available in tree for any distro or > site that really wants it. I think its time for the needs of the many to > outweigh the needs of the few … and those who want to stick with the SYSV > printing stuff are definitely the few (albeit a vocal few). > > (There may be *other* changes that limit OmniOS from building stock > illumos-gate -- I'm not at the moment immediately aware of any aside from the > printing problem.) > > I am aware of two others -- which we don't miss at all: > > https://github.com/omniti-labs/illumos-omnios/commit/bb305766ac54716fb8590b7ed18d49ba6fafddfa That one shouldn't break the gate… we should fix that. (That said, I don't understand the motivation for that removal… its a point of curiosity for me.) > https://github.com/omniti-labs/illumos-omnios/commit/d669e004b58c74cfd5f5128c40dfea28a9b6a6a6 That seems to just support the above. Would it have been easier to use uname ? > > Additionally, our perl updates require a spattering of updates to the > illumos-gate build (which should likely be made more flexible and elegant). Yes yes yes! I mostly want to eliminate the use of perl in illumos-gate, but that's much harder. The biggest challenge is the perl extensions we deliver, which IMO have very limited value, but that's another discussion…. > > The other problem with using OmniOS for this is that OmniOS is totally > controlled by a single commercial entity, which is distasteful for some > people. As for myself, I'd be willing to overlook that and accept that if > Omni ever decided to go seriously astray we could always fork *their* work. > I don't see that being likely any time soon though. > > This is of course a concern for the community, but I agree that it could be > forked without issue. > > Bryan's mentions of OmniTI's concerns are partly valid. We do tend to move > quickly and take liberties in our "bloody" release that are likely more risky > than some would care for. Having OmniOS become the reference distribution > for Illumos was an original goal of OmniOS, but coupling the development of > OmniOS with the Illumos community as a whole (and its governance) would > likely restrain OmniTI in ways that aren't in its interest. > > To sum up, I think it would be great to use OmniOS r151006 as the reference > implementation. I can say that we have no desire to make changes to OmniOS > going forward that would break the gate. Additionally, the risk for the > community is very low. If at some point r151006 becomes too dated or less > relevant, you can move to the next distribution and that could be a future > OmniOS release or another contender. Excellent. I think we should consider this. Again we have to agree to kill off the legacy SYSV printing… but this is a topic we can take up in developer council. There are one or two people who have wailed in the past when this came up, but really, its time to recognize that this doesn't belong in illumos-gate anymore. Almost nobody uses it, and it is costing us to keep it around -- its time to kick it out. Those who still want it can take the sources into a separate repo, if they like. - Garrett ------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
