Mail bounced first time so forwarding again ...
---------- Forwarded message ---------- From: Moinak Ghosh <[email protected]> Date: Wed, Jul 14, 2010 at 9:45 PM Subject: Re: [distribution-discuss] [osol-discuss] Community distro To: Dennis Clarke <[email protected]> Cc: Alan Coopersmith <[email protected]>, Open Solaris <[email protected]>, [email protected] On Wed, Jul 14, 2010 at 8:06 PM, Dennis Clarke <[email protected]> wrote: > > ----- Original Message ----- > From: Alan Coopersmith <[email protected]> > Date: Wednesday, July 14, 2010 10:25 am > Subject: Re: [osol-discuss] Community distro > To: [email protected] > Cc: Rob McMahon <[email protected]>, Open Solaris > <[email protected]>, [email protected] > > [...]> > Do we care anymore ? > >> be removed from more of the source gates as more consolidations transition. >> >> If others want to work on a distro that doesn't have that issue, they >> should be free to do so. > > Look, dear Alan, I said and I say again .. to hell with the SVR4 issue. That > is way way up the stack of issues. Start at the bottom. The closed sources > and the i18n issues. Start there. Because right now there is NO way that > anyone outside of Oracle can build OpenSolaris without internal people > working on closed code bits. > > Now tell me where I am wrong in that statement. > > After five years this "open source" project is still strung up in *critical* > closed bits. > Lets not get worked up here with packaging issues. So many of us have complained in the past only to be shown the highway - in any case Osol distro was a SUN project and SUN did as it deemed fit. I have zero love for IPS but as it is today it works and is a good starting point at least for the time being. Subsequently it is highly possible to write an "alien" translator that can convert from IPS to some other packaging format using manifest metadata. SVR4 from a high-level specification perspective is good but the present implementation is horrid. I have worked with that codebase during my SUN-days and I know. Things like custom class-action scripts, no facility of package upgrade, flat file contents list are simply broken. the codebase is crazy mix of C and shell scripts. That does not mean that the spec cannot be updated in a few places and the whole thing rewritten from scratch in Python or whatever other language (Python is eminently suitable for application and system programming btw). Regards, Moinak. -- ================================ http://www.belenix.org/ http://moinakg.wordpress.com/ -- ================================ http://www.belenix.org/ http://moinakg.wordpress.com/ _______________________________________________ distribution-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/distribution-discuss
