Date: Sat, 29 Feb 2020 19:44:40 +0000 From: Bob Eager <rde@tavi.co.uk> To: freebsd-ports@freebsd.org Cc: portmaster@BSDforge.com Subject: Re: When to use TMPPLIST instead of pkg-plist? Message-ID: <20200229194440.70ad674e@raksha.tavi.co.uk> In-Reply-To: <a38ed7c362f0e941a4e76616d9df599f@udns.ultimatedns.net> References: <a78ca75b-1596-ce0e-ccd5-f21210e16045@FreeBSD.org> <a38ed7c362f0e941a4e76616d9df599f@udns.ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 29 Feb 2020 11:29:18 -0800 Chris <portmaster@BSDforge.com> wrote: > TMPPLIST is an artifact of the QA process when making a port. 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. When a > discrepancy occurs. You're warned, and instructed to make changes as > required. The thing is, because of so many variables, that TMPPLIST > isn't always correct. So to rely on it, as Mathieu stated, would be > *bad* policy. As memory serves; it's also the product of make > make-plist. make makeplist I believe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200229194440.70ad674e>