Possible unzip dependency bug with a PREFIX set

[Steven Harris]

Thanks Matthew - yeah it was easily worked around with a couple of quick
symlinks, and i had the suspicion that behaviour might have
been intentional.

Cheers

Steve

On Fri, Dec 21, 2012 at 11:47 AM, Matthew Seaman <matthew at freebsd.org>wrote:

> On 21/12/2012 01:25, Steven Harris wrote:
> > One a clean install of FreeBSD, i wanted to install openjdk7 into
> > /share/local (which is later exported through NFS).
> >
> > Installing other ports (apache, php etc) works perfect, but openjdk7
> relied
> > on unzip.   So as a dependency, it installed unzip from ports, but
> because
> > of my PREFIX setting, put it in /share/local/bin/unzip
> >
> > Then after returning to openjdk, it was specifically looking in
> > /usr/local/bin for unzip.
>
> This is normal.  The ports system looks for whatever it needs to install
> a port under ${LOCALBASE}/ and it will install the port to ${PREFIX}/
>
> Usually, ${LOCALBASE} and ${PREFIX} are set to the same value:
> /usr/local.  Having them set to *different* values only works for
> installing the one single port at the tip of the dependency tree: it's
> handy for port maintainers to test the port with, but not a lot else.
> Things get very ugly very quickly if you try and install
> port+dependencies without ${LOCALBASE} == ${PREFIX}.
>
>         Cheers,
>
>         Matthew
>
> --
> Dr Matthew J Seaman MA, D.Phil.
> PGP: http://www.infracaninophile.co.uk/pgpkey
>
>
>