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.
-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
>>
