Nicolas Williams wrote: > While I agree with this fix, I wonder if the RPATH recorded in > _mysql.so is correct. Do we really expect that if /usr/mysql/lib > changes to point to /usr/mysql/5.x/lib that _mysql.so will continue to > work? Or does _mysql.so need to be rebuilt if MySQL gets revved? > > If there is a bug in how _mysql.so is built then that should be filed > and made a see also of this one.
Looks like this was discussed during the MySQL 5.0 ARC case. See: http://mail.opensolaris.org/pipermail/webstack-discuss/2007-October/000490.html Comment from Jyri Virkki:** >/ /usr/mysql/ will expose bin, include, lib, man, share, and src / >/ directorie s.These will be symbolic links to corresponding directories / >/ in the highest numb ered <version>.<subversion>.<minor-subversion> / >/ directory in /usr/mysql hence, u sers will be able to use / >/ "/usr/mysql/bin/mysqld" to invoke the most recent vers ion. / Be aware that previous cases like PHP considered and rejected this symlinking. Will the documentation recommend writing scripts which invoke /usr/mysql/bin/mysql for example? What happens when an incompatible version (be it 5.1 or 6) is installed? Other components like perl do provide this linking. So it's been done both ways. My suggestion is to consider the use cases carefully and include a paragraph in the case explaining the reasoning of your choice, whichever approach you choose. I think this is above and beyond the scope of bug #3395. If you think there is a bug here, I suggest you submit it. _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
