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 09F9313877A for ; Thu, 3 Jul 2014 08:47:53 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 18CBAE0881; Thu, 3 Jul 2014 08:47:48 +0000 (UTC) Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by pigeon.gentoo.org (Postfix) with ESMTP id 316BFE0858 for ; Thu, 3 Jul 2014 08:47:47 +0000 (UTC) Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19]) by qmta10.westchester.pa.mail.comcast.net with comcast id Mknm1o0030QuhwU5Aknm3z; Thu, 03 Jul 2014 08:47:46 +0000 Received: from [192.168.1.13] ([50.190.84.14]) by omta02.westchester.pa.mail.comcast.net with comcast id Mknm1o0040JZ7Re3NknmhG; Thu, 03 Jul 2014 08:47:46 +0000 Message-ID: <53B518A5.7030605@gentoo.org> Date: Thu, 03 Jul 2014 04:47:33 -0400 From: Joshua Kinard User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] new profile layout with flavors and mix-ins References: <20140702154416.GA1151@linux1> <20140702195437.09c8efdb@pomiot.lan> <53B4F5AF.9020600@gentoo.org> <53B4FF82.4020309@gentoo.org> In-Reply-To: <53B4FF82.4020309@gentoo.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1404377266; bh=U/GQE/y0Zgmh0pPO9/5Yb61srldO42dY03NlOXGgJFk=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=mMiOOYcO2qGLOCE/Sn2JZlnLJeFbB4sQce9yLbZ4II0FU27fATlJjZFfqFOwvBSD6 K6e31tcfWnOv+UhzJqISC7LQX4AMy+O0gTcZHnuyQ9VDkE2KHl87GpbG7cxYnjMHIw vjiZXthTBEN8OfBgiWnuSJc/hEcTKazCnTEMNJ4siMqR8ilz+hr82xPq3epcRqJZYx xJqlm+madbYhr5Ikbs1vGP18O+Gki2c7D0jcBBGP1OiA7+A+c2pfo0HfLodT/5aao0 SNftn5cabcTucOCUqnK3is9GfKnsngSoO0A0Kdkn8yB6hUaq7IYr92HmIHOo7cEJJI pNVxu9aD+nsaw== X-Archives-Salt: 974a6af4-119d-400b-9837-8a90d26b4f77 X-Archives-Hash: c7cc709a363b3fb2ef88398989fde01c On 07/03/2014 03:00, Michael Haubenwallner wrote: > > On 07/03/2014 08:18 AM, Joshua Kinard wrote: >> On 07/02/2014 13:54, Michał Górny wrote: >>> Dnia 2014-07-02, o godz. 10:44:16 >> [snip] >>> >>> I don't feel like we ought to vote on something like this without >>> understanding most of the current profiles. And I'm afraid there are >>> only few people who have any idea about the current profile >>> structure... >>> >> >> I am going to throw this out there and see what people think. Maybe it's >> insane, maybe it's not, maybe it's a mix of insane and not-insane. >> >> Years ago, before we had the current stacking profile design (we were >> discussing the current design, actually), I kinda conjured up this "building >> blocks" like approach for a profile design. > >> The idea being that, in /etc/make.conf (or wherever that file is now), you'd >> define $PROFILE like this: >> >> linux-mips o32 uclibc server: >> PROFILE="base:kernel/linux:arch/mips:subarch/mips-o32:libc/uclibc:roles/server:releases/13.0" > > What about making /etc/portage/make.profile a directory rather than a symlink, > having /etc/portage/make.profile/parent to reference all the flavours? > > Tools that need to respect the /current/ profile should work without any change, and > tools that need to respect the /available/ profiles (repoman) already do have a list > of profiles to respect (profiles/profiles.desc). > > So the only missing thing would be the eselect profile module to manage entries of > /etc/portage/make.profile/parent, maybe using /usr/portage/profiles/profiles.desc > as the source for available flavours. > > my 2 cents > /haubi/ That's the thing, make.profile technically *is* a directory -- a symlink to one. The original design of make.profile was to specify generic, base settings for a given profile and keep that in the tree. Things like default CHOST, default ARCH, default , etc. make.conf then overrides in-tree settings with settings specific to your system. So making /etc/make.profile an actual directory disconnects it from the tree, which I don't think will work very well for Portage, since it won't know what your currently-chosen profile is. -- Joshua Kinard Gentoo/MIPS kumba@gentoo.org 4096R/D25D95E3 2011-03-28 "The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between." --Emperor Turhan, Centauri Republic