Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 7 Aug 2006 18:10:32 +0100
From:      Shaun Amott <shaun@FreeBSD.org>
To:        "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: Ports defying WRKDIRPREFIX
Message-ID:  <20060807171031.GA58639@picobyte.net>
In-Reply-To: <44D71068.1000102@gmx.de>
References:  <44D70E2F.8060008@gmx.de> <20060807100144.GG38697@graf.pompo.net> <44D71068.1000102@gmx.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 07, 2006 at 12:05:28PM +0200, [LoN]Kamikaze wrote:
>=20
> Thierry Thomas wrote:
> > Le Lun  7 ao=FB 06 =E0 11:55:59 +0200, [LoN]Kamikaze <LoN_Kamikaze@gm=
x.de>
> >  =E9crivait :
> >> It has come to my attention that the line
> >>
> >> 	${CAT} pkg-message
> >>
> >> breaks when WRKDIRPREFIX is set, because the shell command will be i=
nvoked
> >> from WRKDIRPREFIX/PORTSDIR/category/port instead of PORTSDIR/categor=
y/port
> >>
> >> I think this is a new problem in bsd.port.mk, but I am not certain a=
bout
> >> this. A quick solution is to replace the line with
> >>
> >> 	${CAT} ${.CURDIR}/pkg-message
> >=20
> > @${CAT} ${PKGMESSAGE}
> > should be sufficient.
>=20

I've fixed deskutils/multi-backgrounds-daemon, net-im/jabber-aim and
devel/libtap, but the other unmaintained ports redefine PKGMESSAGE; so
they will need a different fix.

--=20
Shaun Amott [ PGP: 0x6B387A9A ]
    Scientia Est Potentia.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060807171031.GA58639>