Date: Tue, 11 Jan 2000 14:11:50 +0100 From: Alexander Langer <alex@big.endian.de> To: "Chris D. Faulhaber" <jedgar@fxp.org> Cc: Bill Fumerola <billf@chc-chimes.com>, freebsd-ports@FreeBSD.ORG Subject: Re: ports/16017: BitchX IRC client port upgrade Message-ID: <20000111141150.A7264@cichlids.cichlids.com> In-Reply-To: <Pine.BSF.4.10.10001110747300.28839-100000@pawn.primelocation.net>; from jedgar@fxp.org on Tue, Jan 11, 2000 at 07:54:42AM -0500 References: <20000111133845.E2722@cichlids.cichlids.com> <Pine.BSF.4.10.10001110747300.28839-100000@pawn.primelocation.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Chris D. Faulhaber (jedgar@fxp.org):
> > > > + ${ECHO} @dirrm share/doc/BitchX >> ${PKGDIR}/PLIST
> > > > + ${ECHO} @dirrm lib/bx/plugins >> ${PKGDIR}/PLIST
> > > > + ${ECHO} @dirrm lib/bx >> ${PKGDIR}/PLIST
> > > I'm reasonably sure that ${PKGDIR} has to remain read-only during
> > > package builds. There are better ways to do this.
> > Uhm. I know the PLIST= one, but creating the PLIST dynamically is just
> > nice and saves space.
> That may be, but with the above code, your PLIST will be completely out of
> whack if you build/install the port more than once. The suggested way
I thought so, too, when I took a look at the port for the first time,
but at this time that wasn't the case, because some more above he cp's
PLIST.common to PLIST, which makes a _fresh_ copy of PLIST.
> (according to http://www.freebsd.org/handbook/porting.html 4.4.13.4) would
> be to edit ${TMPPLIST} in the post-install target.
Nice. I have used dynamic PLIST's in some ports too and will soon
switch then, I think ;-)
It seems I have not seen this section in the porting.{sg,ht}ml when I
checked the last time.
Alex
--
I doubt, therefore I might be.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000111141150.A7264>