[arc-discuss] Defining OpenSolaris Consolidations

James Carlson james.d.carlson at sun.com
Tue Aug 7 10:02:25 PDT 2007


Stephen Hahn writes:
> * Alan Coopersmith <alan.coopersmith at sun.com> [2007-07-13 10:45]:
> >   6) That only one Consolidation at a time may deliver the same component
> >      (file) to the system at a given location.
> 
>   Aha.  This requirement dodges the charter question in a technical
>   fashion, but doesn't talk about charter overlap.  (Overlap and the
>   possibility of removal of Consolidation status are related.)

That makes sense as a basic packaging constraint, but the existing
architectural requirements are stronger than that.  From 1991/061:

  http://www.opensolaris.org/os/community/arc/policies/shared-sharable/

Not only can you not deliver to the same location as some other
consolidation, but (unless you get an architectural exemption) you
can't redeliver the same thing or a modified version of the same thing
to some distinct location.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677


More information about the arc-discuss mailing list