I've added companion-discuss to the discussion. And I've added Laca from the JDS group, since he's working on a project[1] that should make it easier to keep third-party apps current. For those folks: this thread was started by Brian Gupta's observation[2] that there are several overlapping projects that deal with third-party open source code and (Open)Solaris and maybe things could be done more efficiently.
>>>>> "jek3" == Joseph Kowalski <jek3 at sun.com> writes: jek3> I think the concept of CCD is simply bad. We should not be jek3> providing a recompilation and packaging service. We should be jek3> providing assistance to the ultimate code maintainers to provide jek3> Solaris "packages" just like they provide RPMs (or whatever) for jek3> Linux. Let's turn our "recompile" junkies into "Solaris Packaging jek3> Evangelists" (easier said than done - different skill set - but jek3> hopefully you get the idea). The upstream maintainers will need Solaris boxes (SPARC and x86) in order to produce Solaris packages. I'm skeptical that they will be enthusiastic about this. jek3> Second, there is an unavoidable latency introduced by placing a jek3> "CCD" service in the loop. Up through Solaris 10 the Companion had a horrible latency problem, because we only shipped new bits with each Solaris update release. Now it has a smaller latency, which is the time to download the latest upstream source, tweak local patches as needed, rebuild and sanity-test, then push new packages to opensolaris.org. jek3> The Linux distros don't have this latency. They didn't have the first one that I mentioned, but I believe they do have the second one. mike [1] http://mail.opensolaris.org/pipermail/companion-discuss/2007-April/000522.html [2] http://mail.opensolaris.org/pipermail/sfwnv-discuss/2007-May/000380.html
