well,, there are multiple potential "issues" at play here. on the one hand, I understand your frustration at not having it normally in the path. But what would be the side effects of having a symlink /opt/csw/bin/mysql -> /opt/csw/mysql5/bin/mysql ?
Would it break auto-detection of mysql location, when compiling? and... is that ok anyway, since we dont have auto-detection now anyway? :-) It may indeed be appropriate to adjust our mysql5 package to have the symlink in there. BTW: would you be intersted in taking over our mysql package, for purposes of updating, and putting the symlink in there? (pleasepleasepleaseplease? :-) On Tue, Sep 8, 2009 at 1:33 AM, Maciej (Matchek) Blizinski <[email protected]> wrote: > Most packages put their files in /opt/csw; but some seem to be > special, and use /opt/csw/${something}. For instance, MySQL 5 uses > /opt/csw/mysql5. I understand that it's a way of having multiple > versions of MySQL on one system at the same time, but it's somewhat > annoying to not have the mysql binaries in the PATH right after > installation. Was /opt/csw/mysql5 with a separate bin with no symlinks > from /opt/csw/bin a solution that was a result of a discussion, or was > is only because the maintainer just did it this way? > > Maciej > _______________________________________________ > maintainers mailing list > [email protected] > https://lists.opencsw.org/mailman/listinfo/maintainers > _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers
