Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 29 Feb 2020 12:59:47 -0800
From:      Chris <portmaster@BSDforge.com>
To:        Bob Eager <rde@tavi.co.uk>
Cc:        <freebsd-ports@freebsd.org>
Subject:   Re: When to use TMPPLIST instead of pkg-plist?
Message-ID:  <c59073f1dcc8801421d87509dc8b3863@udns.ultimatedns.net>
In-Reply-To: <20200229194440.70ad674e@raksha.tavi.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 29 Feb 2020 19:44:40 +0000 Bob Eager rde@tavi=2Eco=2Euk said

> On Sat, 29 Feb 2020 11:29:18 -0800
> Chris <portmaster@BSDforge=2Ecom> wrote:
>=20
> > TMPPLIST is an artifact of the QA process when making a port=2E It is
> > used for comparison to what you, as a port maintainer claim is the
> > pkg-plist, and whats found that looks as the actual plist=2E When a
> > discrepancy occurs=2E You're warned, and instructed to make changes as
> > required=2E The thing is, because of so many variables, that TMPPLIST
> > isn't always correct=2E So to rely on it, as Mathieu stated, would be
> > *bad* policy=2E As memory serves; it's also the product of make
> > make-plist=2E
>=20
>  make makeplist
>=20
> I believe
You believe correctly=2E :)
funny it doesn't show up in man ports=2E

Thanks for the correction, Bob!

--Chris





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