Oops I forgot to add in my opinion ;-) in my reply!!!!!!. Thanks a lot Steve to correcting me (well i am not a part of companion-discuss alias so I was not sure of this) Also its good to know active work is going on and would it be possible to add Compiz in your build environment?
Apologies again for sending a reply without proper knowledge. ~Saurabh Steve Christensen wrote: > Incorrect - > > see > > http://opensolaris.org/os/project/companion/ > > The Companion files are available for NV build 56 now and 62 shortly > (I have a clean test build of the current svn repository for the > Companion done on NV 62 for x86 and a SPARC one soon.) > > Steve Christensen > > > Saurabh Vyas wrote: >> Erwann Chenede wrote: >>> Hi Alan & Saurabh, >>> >>> Thanks for the clarification. >>> >>> Compiz only works on nevada. Is there already a companion CD for >>> SDX releases ? >> As of now there is no activity on companion CD front for nevada (the >> work had stopped after S10 release). >> But I feel it would be good idea to revive this distribution >> mechanism (I guess the build mechanism used there is bit old and it >> we do have spec-files-extra which uses `pkgbuild ` which a good >> framework to build packages for Solaris). >> Well again the whole idea is to provide users with easy access to >> `cool` things like Compiz on Solaris. >> >> ~Saurabh >> >> PS : Now the neveda distribution is called SxDE (Solaris Express >> Developer Edition!!!!!) ans SDX ;-) . >> >>> >>> Thanks, >>> >>> Erwann >>> >>> Alan Coopersmith wrote: >>>> I mean that if you call Sun support to report a bug, they will >>>> tell you it's unsupported. If a bug is found, there is no >>>> mechanism to deliver a patch, just wait for the next version >>>> of the Companion CD, which comes out only when a new Solaris >>>> update release is issued, and if you've got a bug in the Solaris 8 >>>> or Solaris 9 companions, you're simply out of luck - since there >>>> are no more Solaris 8 or 9 update releases, there will never be >>>> any more Companion CD bug fixes. >>>> >>>> (These are among the reasons blastwave was originally created as >>>> independent of the Companion CD, despite the communities desire >>>> to build on the Companion CD, since it was simply unsustainable.) >>>> >>>> If the Companion plans to change from the way it's been handled for >>>> the past 5 years that would be great, but given the incredibly meager >>>> funding for it by Sun, and lack of community support, I would be very >>>> surprised to see that happen. >>>> >>>> -Alan Coopersmith- alan.coopersmith at sun.com >>>> Sun Microsystems, Inc. - X Window System Engineering >>>> >>>> Steve Christensen wrote: >>>>> Alan - >>>>> >>>>> Not sure what you mean by "absolutely none". All of the current >>>>> Companion packages are in the process of being updated to their >>>>> latest versions and, as far as I know, this will continue and be >>>>> completed soon. If a package gets put on the Companion through >>>>> the processes already defined for adding to the Companion, they >>>>> will be both updated and supported - at least that is my >>>>> understanding. The only way I know of that this might not happen >>>>> is if Companion packages are dependent on something from other >>>>> consolidations or projects and these do not get updated. >>>>> >>>>> Steve Christensen >>>>> >>>>> >>>>> Alan Coopersmith wrote: >>>>>> Erwann Chenede wrote: >>>>>>> This could be a good delivery mechanism. What's the support >>>>>>> level expected from packages included in the companion cd (e.g. >>>>>>> in term of sustaining, etc.) >>>>>> >>>>>> Absolutely none - not even a promise to deliver new versions if >>>>>> major >>>>>> bugs or security holes are found. >>>>>> >>>> >>>> _______________________________________________ >>>> desktop-discuss mailing list >>>> desktop-discuss at opensolaris.org >>> >>> >> >>
