Hello, Well, it would make sense to just use the latest 'dev' release or 'tested' release if support or security is a major issue in environments like GOV. Most packages can be updated per user as the patches and scripts are available to review. If more support is needed, then a support contract is usually the way to go if this only becomes beneficial if you have a production environment and need critical fixes from Oracle that cannot be accomplished by in-house staff. Commiting one of Oracle's "responsible engineer(s)' to maintain the other repositories outside of the currently available ones may cause more pain than gain. Best to report in defect.opensolaris.org and then get the actually package updated or fixed in /dev. Or, someone can have another in-house IPS that commits to this single purpose. ~ Ken
--- On Thu, 3/18/10, Rand S. Huntzinger <[email protected]> wrote: From: Rand S. Huntzinger <[email protected]> Subject: Re: [indiana-discuss] Free /support, /security repository for 2010.x, wider OpenSolaris usage. To: [email protected] Date: Thursday, March 18, 2010, 8:02 AM In my opinion, the lack of security and other critical fixes to the release repository severely limits its usefulness. Before the six month release cycle is complete somebody is bound to be breathing down my neck asking why such and such security fix hasn't been applied. To keep up to date with security fixes you have to use the dev release which brings along with it lower stability. So - yes, I think you should do this. As far as I'm concerned, there is no need to start providing updates with 2009.06, starting with the next release would be fine. -- Rand -- This message posted from opensolaris.org _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
