Date: Mon, 23 Mar 2015 20:44:58 +0100 (CET) From: Gerald Pfeifer <gerald@pfeifer.com> To: Bryan Drewery <bdrewery@FreeBSD.org>, Mathieu Arnold <mat@FreeBSD.org> Cc: Sunpoet Po-Chuan Hsieh <sunpoet@freebsd.org>, svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r381968 - head/lang/gcc5 Message-ID: <alpine.LSU.2.11.1503232038520.15042@tuna.site> In-Reply-To: <551061EC.5090702@FreeBSD.org> References: <201503222311.t2MNBE8d075929@svn.freebsd.org> <CAMHz58SEVfiUsrz0f2dMVsvA-kL4e%2BTF2JcuzYBp7bPPEYsCow@mail.gmail.com> <551061EC.5090702@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 23 Mar 2015, Bryan Drewery wrote:
>> USE_LDCONFIG stores the directory name to
>> ${LOCALBASE}/libdata/ldconfig/${UNIQUENAME}.
>> Since lang/gcc* now share same PORTNAME (gcc), you need to
>> set UNIQUENAME manually.
> I just hit this. I've fixed it in r382022.
Thanks for fixing this, Bryan, but...
...doesn't this point to a design problem with the infrastructure?
Mk/bsd.ports.mk says:
# UNIQUENAME - A name for your port that is globally unique. By default,
# this is set to ${LATEST_LINK} when LATEST_LINK is set,
# and to ${PKGNAMEPREFIX}${PORTNAME} otherwise.
# PKGNAMESUFFIX - Suffix to specify compilation options or a version
# designator (in case there are different versions of
# one port as is the case for Tcl).
If PKGNAMESUFFIX is used as Mat suggested (to carry a version number),
shouldn't it become part of UNIQUENAME? Can this be improved?
If not, I guess I should just revert PORTNAME to gcc47, gcc48, and
so forth. Using PKGNAMESUFFIX is not providing the expected benefit.
And things just are becoming more complex. :-(
Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LSU.2.11.1503232038520.15042>