Hi David,

David.Comay at Sun.COM p????e v ??t 26. 02. 2008 v 09:33 -0800:
> > I know, but Squid 3.0 is a bit different from 2.x line, so Companion
> > could serve as "testing" platform for SFW here.
> 
> Given the move towards a network repository based packaging system, I
> think the right thing to do is include Squid 3.0 as a separate version
> in that repository.  That can most easily be accomplished by
> incorporating that version into SFW alongside the existing 2.6
> version.  Perl is an example of such a component (although it currently
> is delivered out of ON, the principle is the same.)
> 
> At this point forward, I don't see a need to continue adding components
> into the Companion CD for Nevada.  Instead, those components should be
> integrating into SFW (as part of the modernization work a number of us
> have been working on, we intend to support tagging packages with who
> supports them along with perhaps a support level.)
> 

There are severel possible issues with integration in SFW:

a) to complete PSARC for software which could be considered as not so
stable (more in development process)

b) on running system you don't need both Squid versions as opposite to
Perl or Apache, but with integration to SFW (/usr) you will need to
solve this co-existence. With "experimental" CCD (/opt) it will be
easier

c) SFW mess itself (large repository of independent components in one
big nightly)

I understand that CCD should die, but there is already some Squid in
CCD, so no new software will be added. And there is no "experimental"
version of repository in osol.org yet, just SFW. CCD could serve in such
way for some time. Also CCD could be exported as separate IPS
repository.

But yes, just an idea, nothing more :-)

Best regards,

Milan


Reply via email to