From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 690C2138247 for ; Tue, 21 Jan 2014 03:26:59 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 98556E0D5E; Tue, 21 Jan 2014 03:26:58 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E384FE0D56 for ; Tue, 21 Jan 2014 03:26:57 +0000 (UTC) Received: from vapier.localnet (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id DFA1533FA0E; Tue, 21 Jan 2014 03:26:56 +0000 (UTC) From: Mike Frysinger Organization: wh0rd.org To: gentoo-portage-dev@lists.gentoo.org Subject: Re: [gentoo-portage-dev] layout.conf: What's our opinion? Date: Mon, 20 Jan 2014 22:27:00 -0500 User-Agent: KMail/1.13.7 (Linux/3.12.1; KDE/4.6.5; x86_64; ; ) Cc: Sebastian Luther References: <52DD02FA.3040109@gmx.de> In-Reply-To: <52DD02FA.3040109@gmx.de> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-portage-dev@lists.gentoo.org Reply-to: gentoo-portage-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1551704.3eyg3Pav02"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201401202227.01464.vapier@gentoo.org> X-Archives-Salt: 16ed521f-08d8-4d87-bf10-a3402df40ef2 X-Archives-Hash: 33bec33372e1f29a940a4e2d93db4d5b --nextPart1551704.3eyg3Pav02 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable On Monday 20 January 2014 06:05:30 Sebastian Luther wrote: > Currently layout.conf is not under PMS control. This basically means > that every PM (or version thereof) may support different keys and assign > different meanings to them. Portage's behavior for unknown keys in > layout.conf is to ignore them without a warning. which is correct > The bad thing about this is that some layout.conf keys portage currently > supports, may render the repository unusable for a PM if it doesn't > support them. i don't see that as a problem. alternative PMs can ignore unknown keys, or= =20 they can implement support for the new keys, or the repo owner can avoid ke= ys=20 that don't work across all the ones they want to support. > To avoid this type of breakage in other areas (ebuilds, dependency > resolution, ...) PMS has been created. Since the council demands PMS to > be followed, I would expect that they also want the general idea "of not > breaking things randomly" to be followed. as you said, layout.conf isn't in PMS which means this rule does not apply. > Basically it's either > 1) "We add things as we see fit." or > 2) "We should only add things if absolutely necessary.". [1]. if you want things to be stricter, then you can lobby on the lists fo= r=20 standardizing layout.conf in PMS. that said, i don't think layout.conf is "open season". all user visible=20 additions should be reviewed with an eye towards "is this the best we can=20 reasonably do". =2Dmike --nextPart1551704.3eyg3Pav02 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQIcBAABAgAGBQJS3ekFAAoJEEFjO5/oN/WBCtoP/jPyczvSkFmk2Pip2Yh1szek Ols4C7zpre84ERjzzMYss99ixu0pEeYR26BUMHJfbsYwVZDtAnL3AchH3Wdt+WlS kaxbj3JiGbW8BlXm+aw8AXU1b1DAjHMpolmkDMJwT4ali9oOUH800b/wkPVf54CL pmkf1FB6g/OxbEZ6sAyLUrs9qThcgUHQVVKgtzkPAIbqavRPpigIqnPNc+oQoIei dK4pNMzRnZ7/AfU8fVHB6GuXS0arHIkp5EpTjc6ZeToCKhwlXq5xTtIKV3U9kahv JmuKbK5ybMXFM2mOrY3uQ/CXt2LfTSVjvEzlmPND27hEBpzt66szfIYyrRxqH7zR C9U2Sk5gw5YRLf2xxFFzcy0zE3/+LEjtxnwIAg9R4mdrTwJJG6ogZF7YpR6iZ86X 20cKVqKWp0bhMAHuKyn5mbOcyyiuh1pIcM0DE3VWUj9+UacuWUifFQ/muOz/6Hrz r0ZNJ6z8oQB1Hujvu91dteza/PRpjdVRfSL+YF9bEIaKKMPa9fIksQjNWbAmbCuy lmYcdze8pvyzvcVRGDxG7EIMa7W0P9ntUTVkW5f6AIsQJkm+hcau4LkMWiim5Ynk YkrKW5C4kpBecBmMdd67XSliNajt/OKi2uNFoRY9LGK9XqrWThtw1iF0xmEbeBSA mwzZUabl/TrsReWSKAn9 =HRDH -----END PGP SIGNATURE----- --nextPart1551704.3eyg3Pav02--