public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Vaeth <martin@mvath.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: new profile layout with flavors and mix-ins
Date: Thu, 3 Jul 2014 09:01:47 +0000 (UTC)	[thread overview]
Message-ID: <slrnlra6vq.v6r.martin@epidot.math.uni-rostock.de> (raw)
In-Reply-To: 53B4FF82.4020309@gentoo.org

Michael Haubenwallner <haubi@gentoo.org> wrote:
>
>> 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:[...]"
>
> What about making /etc/portage/make.profile a directory
> rather than a symlink, having /etc/portage/make.profile/parent
> to reference all the flavours?

/etc/portage/make.profile already *is* a directory
(only on most user systems it is currently implemented as a symlink
to a directory from the portage tree, but there is no technical
requirement to do that).

I can assure you (from some requests I got as a maintainer of eix
to implement this correctly) that already quite some people
use such an approach:

They specify in the "parent" file (either in their
/etc/portage/make.profile or in /etc/portage/profiles/...)
all sort of additions to profiles which they have written themselves
for various tasks.

So, technically, all this is already covered by portage and
existing tools; no new magic "PROFILE" variable or similar things
have to implemented, and no tools (like eix) need to be changed.

It might, however, be appropriate to reorganize the profile structure
to support this approach better.

> So the only missing thing would be the eselect profile module
> to manage entries

Yes, if you want a user interface for convenient handling of
such a new profiles style, this would need to be written.
However, such a user interface ("eselect profile"?) is perhaps
overkill: The user should be able to handle a single configuration
file "parent" if it is described in the documentation.
The documentation would need to be updated, of course:
Currently, users have to read pms or similar things to understand
what the "parent" file is for...
Also a news item would be appropriate for such a major change, of course.



  parent reply	other threads:[~2014-07-03  9:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02 15:44 [gentoo-dev] new profile layout with flavors and mix-ins William Hubbs
2014-07-02 17:54 ` Michał Górny
2014-07-02 18:10   ` Rich Freeman
2014-07-02 18:32     ` Anthony G. Basile
2014-07-02 18:35       ` Rich Freeman
2014-07-02 18:41     ` Rick "Zero_Chaos" Farina
2014-07-02 19:07       ` Anthony G. Basile
2014-07-02 19:19         ` Rick "Zero_Chaos" Farina
2014-07-02 19:30           ` Rich Freeman
2014-07-03 14:55         ` Andreas K. Huettel
2014-07-03 23:09       ` Tom Wijsman
2014-07-03 23:35         ` Rich Freeman
2014-07-03  6:18   ` Joshua Kinard
2014-07-03  7:00     ` Michael Haubenwallner
2014-07-03  8:47       ` Joshua Kinard
2014-07-03 16:06         ` Ian Stakenvicius
2014-07-03  8:53       ` [gentoo-dev] " Duncan
2014-07-03  9:01       ` Martin Vaeth [this message]
2014-07-03  7:32     ` [gentoo-dev] " Michał Górny
2014-07-03  8:21       ` Joshua Kinard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=slrnlra6vq.v6r.martin@epidot.math.uni-rostock.de \
    --to=martin@mvath.de \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox