On Mon, Apr 7, 2014 at 10:40 AM, Mojca Miklavec <[email protected]> wrote:
> On Mon, Apr 7, 2014 at 4:22 PM, Brandon Allbery wrote: > > On Mon, Apr 7, 2014 at 10:20 AM, Mojca Miklavec wrote: > >> I see that mysql55 for example installs man pages to > >> $prefix/share/man/mysql55/man1/*.1.gz > >> where they are not really functional. > >> > >> Is that a proper place for these files? / Is there any better place? > > > > If you arrange for them to be in ../share/man or ../man when the private > bin > > directory is in $PATH, they will automatically work. (This assumes there > is > > a private bin directory and not just versioned binaries in > /opt/local/bin. > > For something like mysql, there are going to be enough private binaries > to > > make this a good idea.) > > So if the binaries go to > $prefix/libexec/<port>/<something>/ > it would make sense to put the binaries to > $prefix/libexec/<port>/<man> > ? > Yes. See the heimdal port for an example of just that. > It probably wouldn't be such a bad idea to create a script > $prefix/bin/<portname>-init<version>.sh which would prepend > $prefix/libexec/<port>/<something> to PATH. Or maybe simply create a > script like $prefix/libexec/<port>/<something>/usethisone.sh to do the > same. And then man pages would automatically work ... > I've wanted this for a while. That, or adding support for something along the lines of modules.sourceforge.net. (Unlike port select, this might be automatable.) -- brandon s allbery kf8nh sine nomine associates [email protected] [email protected] unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
