FS#19608 - symlink to absolute path in PKGBUILD gives broken link once installed with pacman --root
Attached to Project:
Pacman
Opened by solsTiCe (zebul666) - Thursday, 27 May 2010, 13:38 GMT
Last edited by Dan McGee (toofishes) - Thursday, 27 May 2010, 13:54 GMT
Opened by solsTiCe (zebul666) - Thursday, 27 May 2010, 13:38 GMT
Last edited by Dan McGee (toofishes) - Thursday, 27 May 2010, 13:54 GMT
|
Details
I gave a corrected PKGBUILD on AUR and the maintainer
ignored a second fix I was providing.
He used ln -sf /usr/share/icons/hicolor/48x48/apps/$pkgname.png $pkgdir/usr/share/pixmaps/$pkgname.png instead of ln -sf ../icons/hicolor/48x48/apps/$pkgname.png $pkgdir/usr/share/pixmaps/$pkgname.png So I wondered if I was right to use relative symlink. By building a test package and installing it with pacman --root somewhere, I verified the symlink is broken. when using an absolute path. My point of view is that all the PKGBUILD that use absolute symlink are broken. I ask you : is it a bug of pacman ? is it desirable that pacman is fixed to work around that ? |
This task depends upon
Closed by Dan McGee (toofishes)
Thursday, 27 May 2010, 13:54 GMT
Reason for closing: Not a bug
Additional comments about closing: Haha, I didn't think it would be that easy to convince you. :)
Closure Request: Reason for request: OMG. I'm splitting hairs. again. Dan is right. please close this
Thursday, 27 May 2010, 13:54 GMT
Reason for closing: Not a bug
Additional comments about closing: Haha, I didn't think it would be that easy to convince you. :)
Closure Request: Reason for request: OMG. I'm splitting hairs. again. Dan is right. please close this
Pacman *will not* rewrite absolute symlinks, even if installed with --root. That just doesn't make any sense. The only point of the --root option is to have that spot in your filesystem later be used for either a running system or a place to chroot.