Subject: pkgtools -- please do not hard code path
To: None <firstname.lastname@example.org>
From: Jan Danielsson <email@example.com>
Date: 05/13/2007 19:18:16
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
Content-Type: text/plain; charset=ISO-8859-1
I have pkg_comp set up to build binary packages so I don't have to
remove half my system when I update common libraries.
For partitioning-technical reasons, I have pkgsrc in /home/pkgsrc.
pkg_comp maps /home/pkgsrc/pkgsrc to /usr/pkgsrc in the chroot. For
almost all applications, this hasn't caused any major problems. But one
application which does not work properly when I install from the binary
package built in the chroot is lintpkgsrc. When I installed pkglint in
my "real" system from the binary package, I can no longer run
lintpkgsrc, since it's hard coded to use /usr/pkgsrc.
One solution is to simply link /usr/pkgsrc to /home/pkgsrc/pkgsrc.
But when I discussed this on IRC, someone pointed out that applications
which hard code the pkgsrc path during installation aren't being well
behaved. When I think about it, I agree with that. The pkgsrc path
should be queried in run-time, IMHO. Or is there a reason not to?
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (NetBSD)
-----END PGP SIGNATURE-----