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 0799513877A for ; Thu, 3 Jul 2014 23:36:02 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BD02BE084E; Thu, 3 Jul 2014 23:35:56 +0000 (UTC) Received: from mail-ve0-f172.google.com (mail-ve0-f172.google.com [209.85.128.172]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id BAE02E0814 for ; Thu, 3 Jul 2014 23:35:55 +0000 (UTC) Received: by mail-ve0-f172.google.com with SMTP id jz11so958529veb.31 for ; Thu, 03 Jul 2014 16:35:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=TzswMbd/lDeMtMFBqCebUpY8C1/xzSdzkIxT+ddTl6U=; b=GWXVcA6nAG0t6WgMrxgg6tNxmY4dBdRhYtCI2LmERNjjrTC7Fx1hNKVzEiGS3DxAcP yeM6Sz28yzzeAtWAa1HkwMwYcydQAgYQk02BkOAYmmEoO9PMwaLMEHnk4+KbJrT66KQ6 7/cSCSY5RYEAXrmIuR9ggbJXD2zXPpfOlm6gVlkKVKV690o1YpuDt0d2hl8A1S7+G+C3 cu119xzc2z21gF9e82Q8lub1D07rh3lrkYiqG5DHk/JKBxKBGIGOjbelgHwlLTzj8kZw DByZyNq19jSJum6wzJUMS6f8XEqDdf3r4ahThnq+RP5SynnA0bF1CW5k4hJqhvKDq6bg 1azA== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.52.0.177 with SMTP id 17mr5398220vdf.12.1404430554902; Thu, 03 Jul 2014 16:35:54 -0700 (PDT) Sender: freemanrich@gmail.com Received: by 10.52.72.19 with HTTP; Thu, 3 Jul 2014 16:35:54 -0700 (PDT) In-Reply-To: <20140704010951.3adb4ecf@gentoo.org> References: <20140702154416.GA1151@linux1> <20140702195437.09c8efdb@pomiot.lan> <53B4523F.8040102@gentoo.org> <20140704010951.3adb4ecf@gentoo.org> Date: Thu, 3 Jul 2014 19:35:54 -0400 X-Google-Sender-Auth: YVe5xsNM5cvACQcSmVaZ6zjxWzI Message-ID: Subject: Re: [gentoo-dev] new profile layout with flavors and mix-ins From: Rich Freeman To: gentoo-dev Cc: Rick Zero_Chaos Farina Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 395ac8f2-02de-4330-95d5-bdd032c974c4 X-Archives-Hash: 443c905ce1d5fb24c64e543aa4e95af9 On Thu, Jul 3, 2014 at 7:09 PM, Tom Wijsman wrote: > Did the Funtoo devs tell you that they don't run repoman because of the > explosive set of possible combinations that flavors & mix-ins introduce? > > Having it run over them should be easy; but having it run within a > reasonable time when scaling up is going to be quite painful, ... I don't think we need to check all the combinations. To keep things manageable I think we'd want to define some structure around the profiles and what different kinds of profiles should and shouldn't do. If a profile just pulls in some packages and sets some application-oriented USE flags we shouldn't really need to worry about conflicts - if there are any users will either learn not to run them in combination or at least they won't end up with a completely cripped system if some non-core applications have issues. Messing with ABIs or system-wide configuration settings should be reserved for specific types of profiles which wouldn't be run in combinations unless carefully controlled. We should definitely avoid the mess of inheritance that leads to settings being toggled back and forth. Even if we still end up being stuck with a kernel/arch/subarch hierarchy we'll at least be able to ditch layering on things like kde/gnome further down and open the door to having more variety in our profiles at that level. Something like x32 coming along is fairly rare, even if it is really interesting (and this stuff is one of Gentoo's strong points, actually). There is probably a lot more interest in having more application-level mix-ins in the main tree, or especially in overlays. The reason we avoid them is that today they'd lead to 300 more profiles on top of what is already a big mess. If that part of the tree gets flattened there is no reason somebody could have a minimal profile that doesn't stick openssh in @system, or a bunch of server profiles for various use cases, or some profiles for clusters, config-managed boxes, etc. So, if we come up with a decent strategy, deciding what repoman does and doesn't have to worry about would be part of it. We obviously can't check all the combos, but that doesn't mean that we can't make sure that linux/x86/foo doesn't break. Rich