On Fri, 2007-12-21 at 10:40 -0600, Aaron Griffin wrote:
On Dec 21, 2007 1:44 AM, Jan de Groot <jan@jgc.homeip.net> wrote:
You still haven't looked at the issue with /usr/man/man* getting replaced by a symlink, which is not possible on a system where manpages are already installed.
But that can be covered at a later date. The actual "support" for this is simply unsetting MANPATH. If a package installs man pages to /usr/man/man1 it will still be looked up just fine.
The makepkg 3.1 will no longer move man pages to /usr/man, so I don't think we should do any moving until that is out the door.
Could you explain to me how the symlink will help? It seems like, to me, we're just going to confuse the crap out of pacman when it tries to install/upgrade. With the current implementation, man pages will work regardless of where they are.
Hmm, I must have been mistaken. I read the diff from the commit list, not the whole PKGBUILD. There was something with these two lines coming in: mkdir -p usr/share/man/man{1,2,3,4,5,6,7,8} ln -s man3 $startdir/pkg/usr/share/man/man3x I mistakenly read the ln -s operation on the second line to be a symlink to /usr, where it's actually just a man3x symlink. One thing wrong with this package though: you built it with a broken makepkg, the manpage directories are all moved back to /usr/man :P