I vaguely remember that there was something special about the version on the companion (but that maybe my brain playing tricks on me).
paul Laszlo (Laca) Peter wrote: > On Tue, 2006-12-05 at 10:13 -0800, Marilyn Shoemaker wrote: > > >>when did brltty integrate into the WOS? > > > With GNOME 2.14, so that's snv_42, AFAIR. > > >>Is it just in Nevada or is it also in S10 > > > Nevada only. > > >>any thoughts on how we might track this sort of thing going forward? > > > Hmm... > I was going to say that it's the JDS team that should look out for > these things and review the companion contents when integrating new > stuff into Solaris. But this is really not specific to JDS: other > consolidations may equally decide to integrate a new open source > component and be in conflict with some other consolidation. > So what we really need is some sort of registry of open source > components available in/for Solaris and where they are. > > Laca > > >>Laszlo (Laca) Peter wrote: >> >> >>>Hi Steve, >>> >>>On Tue, 2006-12-05 at 01:52 -0800, Steve Christensen wrote: >>> >>> >>> >>>>This is a code review request for a minor fix in the brltty package. In >>>>the Makefile.sfw for that package, there was a reference to >>>>/opt/sfw/bin/autoconf. In Solaris 10, autoconf was in this >>>>directory, but now it is in /usr/sfw/bin. So a minor change to the >>>>Makefile.sfw has been made to take this into account. The webrev is at >>>> >>>>http://companion.sunfreeware.com/downloads/brlttywebrev/ >>>> >>>>This change allows brltty to build correctly in Nevada 45 without autoconf >>>>in /opt/sfw/bin. >>>> >>>> >>> >>>brltty is already in the WOS (JDS consolidation). >>>Should be removed from the CCD. >>> >>>Laca
