ports/122860: databases/phpMyAdmin installs in the wrong dir

[Matthew Seaman]

The following reply was made to PR ports/122860; it has been noted by GNATS.

From: Matthew Seaman <m.seaman at infracaninophile.co.uk>
To: Ruud Althuizen <ruud at il.fontys.nl>
Cc: freebsd-gnats-submit at freebsd.org
Subject: Re: ports/122860: databases/phpMyAdmin installs in the wrong dir
Date: Sat, 19 Apr 2008 11:25:34 +0100

 This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
 --------------enigB516AC042F0B357B9F877572
 Content-Type: text/plain; charset=UTF-8; format=flowed
 Content-Transfer-Encoding: quoted-printable
 
 Ruud Althuizen wrote:
 > On Thu 17 Apr 2008 08:48 PM, Matthew Seaman wrote:
 >> I can confirm this behaviour, but this is not a problem specific to
 >> the phpmyadmin port.  You'll see this effect with any port using $(WWW=
 DIR)
 >> or $(ETCDIR) if you attempt to override the automatically chosen value=
 s
 >> with any path that isn't a subdirectory of $(PREFIX).
 
 > I can see what you mean. But I found a different port that does what I
 > wanted it to do (twiki). That port sets its own variable TWIKIDIR that =
 will
 > try the default or a user-set dir.
 
 By my reading of the Twiki Makefile, you'ld still end up with essentially=
 
 the same problem.  Twiki defines two variables:
 
 TWIKI?=3D         ${WWWOWN}/twiki        <--- used in PLIST_SUB
 TWIKIDIR?=3D      ${PREFIX}/${TWIKI}     <--- the full location to instal=
 l in
 
 Either of which can be overridden by the user.  If you just override
 TWIKIDIR without ensuring the last however many levels match TWIKI, then
 you'll still end up with a plist that doesn't match what is installed.
 
 Compare this to the standard WWWDIR mechansism as used by phpMyAdmin (lin=
 es
 extracted from bsd.port.mk):
 
 WWWDIR?=3D                ${PREFIX}/www/${PORTNAME}   <--- full location =
 to install in
 WWWDIR_REL?=3D    ${WWWDIR:S,^${PREFIX}/,,}           <--- used in PLIST_=
 SUB
 
 The difference here is that one defines a relative path and then adds
 the PREFIX to it, and the other defines an absolute path and then
 deletes the PREFIX from it if it matches.  That's functionally almost
 exactly the same thing.
 
 There is no good (quick, easy) solution to the problem that I can  see.  =
 If
 I fixed the port so it worked the way you want, it would break things for=
 
 other users.  However, I think your requirement to install web content ou=
 tside
 PREFIX is certainly not unreasonable.  I think I can see a generic way to=
 
 fix this, but it will involve changes to the ports infrastructure which
 will have to go through a lot of review and testing before they could be
 accepted -- all of which will take time.
 
 	Cheers,
 
 	Matthew
 
 --=20
 Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
                                                   Flat 3
 PGP: http://www.infracaninophile.co.uk/pgpkey     Ramsgate
                                                   Kent, CT11 9PW
 
 
 --------------enigB516AC042F0B357B9F877572
 Content-Type: application/pgp-signature; name="signature.asc"
 Content-Description: OpenPGP digital signature
 Content-Disposition: attachment; filename="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.8 (FreeBSD)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
 iEYEAREIAAYFAkgJyKgACgkQ8Mjk52CukIx8eQCfe1d0pZGhfQnxhj8+hgb6kkJS
 FRMAniRc0Wy60d0mEEjWHnURjEC8F5gO
 =0BLe
 -----END PGP SIGNATURE-----
 
 --------------enigB516AC042F0B357B9F877572--