#12151 closed defect (wontfix)
BUG: install doesn't respect --mandir
Reported by: | afb@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | MacPorts 1.5 |
Component: | base | Version: | |
Keywords: | FreeBSD support | Cc: | |
Port: |
Description
When setting --mandir to something like ${PREFIX}/man, it doesn't work but manpages still end up in ${PREFIX}/share/man (due to hardcoding in doc/Makefile). It makes some half-hearted attempt to symlink man to the mandatory share/man, but that doesn't work if "man" directory already exists in install dir ?
Defaulting to ${PREFIX}/share/man and inserting the symlink is fine and dandy, but it should also respect any user overrides. So instead of the Makefile installing manpages into $(DESTDIR)${prefix}/share/man, it should use $(DESTDIR)${mandir} from autoconf.
Attachments (1)
Change History (5)
Changed 17 years ago by afb@…
Attachment: | macports-mandir.patch added |
---|
comment:1 Changed 17 years ago by jmpalacios (Juan Manuel Palacios)
Keywords: | FreeBSD support added |
---|---|
Milestone: | → MacPorts 1.5 |
comment:2 Changed 17 years ago by afb@…
hmm, most of the Ports do hardcode --mandir=${prefix}/share/man anyway so maybe it would be better to try and make the BSD Port/Makefile cope with the man -> share/man symlink instead...
comment:3 Changed 17 years ago by afb@…
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Hardcoding MANPREFIX as ${PREFIX}/share/man instead, and not applying the patch/change.
comment:4 Changed 17 years ago by nox@…
Priority: | Expected → Normal |
---|---|
Summary: | install doesn't respect --mandir → BUG: install doesn't respect --mandir |
Version: | 1.4.40 |
macports-mandir.patch