Alan Coopersmith wrote:
> Not completely (and assuming you mean "the IPS repository on
> pkg.opensolaris.org" when you say IPS, since sunfreeware.com
> & blastwave.org are setting up their own IPS repos as well),
> but the repo team currently has limited time, so the Indiana
> packages come from a very small number of sources - there are
> other bits such as NetBeans, Sun Studio Express, and OpenOffice
> in the repo already that aren't in Nevada, but they're not going
> to set up hundreds of individual delivery paths for all the new
> packages, especially when they're also useful to users of the
> existing Nevada releases.
>
So the two inputs I have to say here are:
1) Stuff that is useful and interesting on pkg.opensolaris.org is not
necessarily useful or interesting (enough) to warrant inclusion in
Nevada, IMO. (This is in part due to the fact that unlike
pkg.opensolaris.org, we have no way to deliver "partial" Nevada -- the
customer has to download, or receive via DVD, the whole kit. Trying to
cram the entire Universe of FOSS onto a Nevada DVD seems -- um --
impractical to me.)
2) If time is of a concern, then maybe by skipping the delivery into
Nevada, delivery of more FOSS via pkg.opensolaris.org could be
*accelerated*. ARC (I think, at the moment) has little interest in
reviewing random bits of FOSS that are in a repository. However, stuff
that make up the Nevada platform (which IMO should be a strict subset of
what is delivered in Indiana -- possibly modulo Install consolidation
bits and bits that are not freely-redistributable) should still be
subject to the regular ARC rules.
If the Indiana folks want to reduce their time to market, I think some
basic investment in Nevada-less delivery will *very* quickly pay dividends.
I'll shut up now -- I think the folks that need to hear the suggestion
will have heard it, and chosen to act or not act on it as they see fit.
-- Garrett
> -Alan Coopersmith- alan.coopersmith at sun.com
> Sun Microsystems, Inc. - X Window System Engineering
>
> Mark A. Carlson wrote:
>
>> The only way to get something into IPS is to go through
>> Nevada first. So all the gates we put on Nevada are required
>> for IPS. You would need to re-swizzle this path in order
>> to change things.
>>
>> -- mark
>>
>> Garrett D'Amore wrote:
>>
>>> Alan Coopersmith wrote:
>>>
>>>> Garrett D'Amore wrote:
>>>>
>>>>
>>>>> (Also, it appears that the
>>>>> Indiana CTeam, if there is one, isn't requiring ARC approval for
>>>>> commitment.)
>>>>>
>>>>>
>>>> There is no Indiana C-Team because there is no Indiana consolidation.
>>>> From the ARC perspective, Indiana is a set of projects targeting
>>>> existing
>>>> consolidations - GNOME, X, Install, ON, SFW, etc.
>>>>
>>>>
>>> So how does IPS get delivered? How about software in IPS format
>>> packages?
>>>
>>> Clearly Indiana is delivering stuff that isn't part of the
>>> "consolidations" that make up Nevada releases. Maybe they have a
>>> W-Team? I don't really know how Indiana is organized.
>>>
>>> But the point is, all ARC authority derives from C-Teams (or other
>>> teams) which require ARC approval. I can only presume (because it has
>>> occurred) that whatever team controls what Indiana ships with has
>>> elected to relax or elide any ARC approval requirement that would be
>>> more typical for Nevada consolidations (ON, SFW, X11).
>>>
>>> -- Garrett
>>>
>>>
>
>
