On Sat, 29 Feb 2020 11:02:23 +0100 Mateusz Piotrowski [email protected] said
On 2/29/20 12:15 AM, Mathieu Arnold wrote:
> On Fri, Feb 28, 2020 at 10:06:19PM +0100, Mateusz Piotrowski wrote:
>> Do we have any (perhaps unwritten) policy for when to use TMPPLIST? And
> when
>> should a port maintainer stick to pkg-plist?
> We do not. A port maintainer should stick to pkg-plist.
That's what I thought.
Is there a reason for it? Does it all boil down to that fact that
pkg-plist is much more explicit and easier to debug/review? Or there is
another reason?
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.
Hope that helps in clarification. :)
--Chris
FreeBSD 14.0-FUTURE #0.000 cray256
Cheers,
Mateusz
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[email protected]"
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[email protected]"
