Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Aug 1998 17:47:19 -0400 (EDT)
From:      Tim Vanderhoek <ac199@hwcn.org>
To:        "David O'Brien" <obrien@NUXI.com>
Cc:        cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Subject:   Re: cvs commit: ports/lang/glibstdc++28 Makefile
Message-ID:  <Pine.BSF.3.96.980817172226.1050F-100000@localhost>
In-Reply-To: <19980817100001.B29597@nuxi.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 17 Aug 1998, David O'Brien wrote:

> On Mon, Aug 17, 1998 at 02:40:16AM -0400, Tim Vanderhoek wrote:
> > Either that, or the bug was that the port leaves too gaping of a
> > window of time where PLIST points to an invalid file.
> > I can't think of any reason a port would need to modify its plist once
> > past the post-build target.
> 
> The bug is not with my port -- the bug is that the new bsd.port.mk tests
> for the existance of PLIST *BEFORE* any of the *-install targets are
> done.  Thus if you frob it in "pre-install", bsd.port.mk won't notice it.

Well, from a simply pragmatic perspective, this gives ports a
chance twiddle their final plist.  Or, perhaps a chance to read
their final plist potentially as an installation guide.

Are their any ports that legitimately need to modify their plist
during *-install?  Usually installation decisions are made during
*-configure...

<shrug>


-- 
This .sig is not innovative, witty, or profund.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980817172226.1050F-100000>