From owner-freebsd-ports@freebsd.org Sun Mar 1 17:02:49 2020 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 97127245CB5 for ; Sun, 1 Mar 2020 17:02:49 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 48VqMs3YD7z3L76 for ; Sun, 1 Mar 2020 17:02:49 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: by mailman.nyi.freebsd.org (Postfix) id 79B03245CB4; Sun, 1 Mar 2020 17:02:49 +0000 (UTC) Delivered-To: ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 79663245CB3 for ; Sun, 1 Mar 2020 17:02:49 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48VqMs2gN9z3L72; Sun, 1 Mar 2020 17:02:49 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from mail.j.mat.cc (owncloud.cube.mat.cc [IPv6:2a01:678:4:1::228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.mat.cc", Issuer "Let's Encrypt Authority X3" (verified OK)) (Authenticated sender: mat/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 3CC111A3EC; Sun, 1 Mar 2020 17:02:49 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from atuin.in.mat.cc (unknown [IPv6:2a01:678:42:ffff:a8da:7b28:799f:765e]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: mat@mat.cc) by mail.j.mat.cc (Postfix) with ESMTPSA id C8384942E97; Sun, 1 Mar 2020 17:02:44 +0000 (UTC) Date: Sun, 1 Mar 2020 18:02:44 +0100 From: Mathieu Arnold To: Chris Cc: Mateusz Piotrowski <0mp@FreeBSD.org>, ports@FreeBSD.org Subject: Re: When to use TMPPLIST instead of pkg-plist? Message-ID: <20200301170244.ic65yhdrmketcy5v@atuin.in.mat.cc> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="2wspeshhr2kamicr" Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Mar 2020 17:02:49 -0000 --2wspeshhr2kamicr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Feb 29, 2020 at 11:29:18AM -0800, Chris wrote: > On Sat, 29 Feb 2020 11:02:23 +0100 Mateusz Piotrowski 0mp@FreeBSD.org said >=20 > > 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. > >=20 > > That's what I thought. > >=20 > > 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 So, I stopped reading there because as this is wrong, all that comes afterwards was also ;-) TMPPLIST is the file where all of PLIST_FILES/DIR go after being processsed for %%FOO%% placeholders, it is where pkg-plist ends up, also after being processed for placeholders. It is also where stuff get added, like .info files from the INFO variable, @ldconfig calls from USE_LDCONFIG, rc file from USE_RC_SUBR, docs and examples from PORTDOCS and PORTEXAMPLES, and probably a few other things pile up in there. All in all, TMPPLIST is the temporary file where every file, directory, keyword... utimately every part of the framework, end up putting what needs to end up in the package. It is also used in the QA process, to tell the user if stuff is wrong wrt what is really installed, but it is not the other way round. --=20 Mathieu Arnold --2wspeshhr2kamicr Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAABCgB9FiEEOraXidLtEhBkQLpbOkUW81GDzkgFAl5b6rRfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNB QjY5Nzg5RDJFRDEyMTA2NDQwQkE1QjNBNDUxNkYzNTE4M0NFNDgACgkQOkUW81GD zkj01g/9GJwQBKL/LDusP4wP6I3EgfrrNs6cVFzqHtou4SJcY4/JnFWFFi3qKmci wzbM2VoVTryLh0c+So4QyOYFPBscBGKvtxBf67O9Gz0CMNXV1f1fGCb9RkWEFDMO g1THNf60nJQaTnPe5k1tlaTByJwAH8IHYRF2zGS89KytZTiSXIBLJd/W/Xjw0/qt 66rII3jdDQIu171QAqYlk+LMD0YRItXPWUagjhXe0lRlftwtGeTPJgEzvbwaDkUS pKh3kYs0NySE8iMmDJvVTK6ijRzRaCHoUJZ1J0sqfB+Q1DIaZ5cbbCwUi1b+ekbU UP1uGFqzte3Ry/zuWa5lQDAUlHbwsNg7mXmv54zp/M8p2McYgwtqRHHao9i+QFgU 1IcRheMen97ddRRJA/heVj33xjz9kmjSl3x+xWHeMKnPsSOkaJSIjkiPoCPVV+C/ TB9yNdeaIl0WABWCUIBnibcT4Cc2AXQJOu6PngLj9+dDaxGKMndixkXJC1ekx5YK 7d9pKjf3E0uf4fovuBR3zAVPpdnQXtlYTK6/4VMca5iowabh5X2StBP2sXXNPMTR CWuD6zV2Wfa1oXmRQ/vlw4PT0EhzB51GWG1F4wVIA7z+btujRm5ZewBPP9zb4gXY gLzGB8jXQhkM23OgIaXYvOXle+Qt3eD13wlAUNfPaD+k330LrlI= =lrEz -----END PGP SIGNATURE----- --2wspeshhr2kamicr--