Date: Wed, 18 Dec 2013 17:45:48 +0100 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Christian Weisgerber <naddy@mips.inka.de> Cc: freebsd-ports@freebsd.org Subject: Re: $FreeBSD$ keywords Message-ID: <20131218164548.GV99753@ithaqua.etoilebsd.net> In-Reply-To: <l8silt$2qj$1@lorvorc.mips.inka.de> References: <l8silt$2qj$1@lorvorc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--sr8SBrQ3fbgntwtR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 18, 2013 at 04:31:57PM +0000, Christian Weisgerber wrote: > What's our policy for putting $FreeBSD$ keywords in the various > files that make up a port? Or rather, what should our policy be? >=20 > By convention, there is a $FreeBSD$ in the port Makefile. Over on > OpenBSD, the policy is to put such keywords into all files that can > hold them: at the top of patch files, with @comment at the start > of plist, etc. In the FreeBSD ports tree, I don't see a consensus > usage. Some people put $FreeBSD$ in all files, some only in the > Makefile. >=20 > What's an undecided committer to do? >=20 > --=20 > Christian "naddy" Weisgerber naddy@mips.inka.de >=20 > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" That should only be on Makefiles for us. regards, Bapt --sr8SBrQ3fbgntwtR Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (FreeBSD) iEYEARECAAYFAlKx0TwACgkQ8kTtMUmk6EwWiACgiUFWYXnhqn9KvSTTfE7YbFxX 2rUAoL7ndJfZoMdaFGu4kS077m0N/qrv =3QR9 -----END PGP SIGNATURE----- --sr8SBrQ3fbgntwtR--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131218164548.GV99753>