Ritu Upcoming Apache 2.2.4 integration does something similar . You can take a look at /net/samp.red.iplanet.com/export/SAMP-GATE/LOCAL-APACHE-GATE/usr/src/pkgdefs/SUNWapch2u/prototype_com
thanks sriram Ritu Kamboj wrote: > David.Comay at Sun.COM wrote: > > >>>> Indeed and it's not clear to me this is actually necessary. Just >>>> deliver the link through the prototype file and upgrade will >>>> automatically move you forward to the latest version. >>>> >>>> >>>> >>>> >>> Not exactly, right? I mean, which ever package is installed last will be >>> the >>> default. I mean, if you install (assumeing) SUNWruby19u first and next >>> SUNWruby18u, then, /usr/bin/ruby would point to version 1.8. >>> Only with the logic in postinstall would you be able to ensure that the >>> /usr/bin/ruby would point to the higest version of ruby. >>> >>> >>> >> Sorry, I wasn't particular clear. I believe the right way of doing >> this is to deliver a link which points to the highest version of Ruby >> that's delivered in the WOS (or in the future, the OpenSolaris package >> repository). If someone wants to access a particular version of Ruby, >> they'll need to access the specific version such as >> /usr/ruby/1.9/bin/ruby. So at any one time, only one package delivers >> that link. >> >> This is similar to the way Perl delivers /usr/bin/perl. >> >> >> > > I wanted to implement something similar for MySQL (ie latest version > points to /usr/mysql directory)...I plan on implementing using > postinstall script ...if the consensus is that updating links in > prototype_com is a better approach, can anyone point me to a reference > implementation for the same > > >> _______________________________________________ >> webstack-discuss mailing list >> webstack-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/webstack-discuss >> >> >> > > _______________________________________________ > webstack-discuss mailing list > webstack-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/webstack-discuss >
