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 C69B2138247 for ; Mon, 20 Jan 2014 11:05:34 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BA010E0BE5; Mon, 20 Jan 2014 11:05:33 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id F3B0BE0BE4 for ; Mon, 20 Jan 2014 11:05:32 +0000 (UTC) Received: from [192.168.11.3] ([88.150.18.76]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0M6fXs-1V98Mp24O4-00wVQd for ; Mon, 20 Jan 2014 12:05:31 +0100 Message-ID: <52DD02FA.3040109@gmx.de> Date: Mon, 20 Jan 2014 12:05:30 +0100 From: Sebastian Luther User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131111 Thunderbird/17.0.9 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 To: gentoo-portage-dev@lists.gentoo.org Subject: [gentoo-portage-dev] layout.conf: What's our opinion? X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:/8/+GIQGspWR2ah/7WIIZd5sz7A/jB9khj3tXYgVX2JXJPipUIz ampPkq8Wad4JsSbUCaosyIhS9S2Q1ZR1xHJQQew4MHU7FCuUbWI9gSPmbKQzdX6I6HYeSg1 bbr0JbpJscZikRhgu+FebJmdBIBF1H3nnXOB+6RHkJL7BDH9X5eloM4mqgqqJNTYYfQNAXh JBFvES2jVhgyQCbNuIQow== X-Archives-Salt: 42c1e6a7-d30e-4b64-818a-be7f6c640443 X-Archives-Hash: 6ed2dc2188852bc6b1c8a2936feb2382 Hi all, ${repository}/metadata/layout.conf is a file that allows a repository maintainer to adjust the package manager's behavior for a repository. I guess the best known is the 'masters' key, but there are lots of other things by now (see man portage). 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. 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. 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. This brings us to reason that made me write that mail. Some days ago Arfrever committed some additions to layout.conf [1], for which he apparently had the ack from Zac from some months ago [2]. After discussing this one IRC I came to the conclusion that we just disagree on how we should handle additions to layout.conf. Basically it's either 1) "We add things as we see fit." or 2) "We should only add things if absolutely necessary.". I obviously would prefer 2) to follow the "things shouldn't break randomly" route. So what's your opinion? Should we go for 1) or 2) or something else? - Sebastian [1] http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=4c409a049c394389b1de398db511380e2fed0437 [2] http://dpaste.com/1560782/