From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Reorganizing handling of target specific profiles (Was: Split desktop profile patches & news item for review)
Date: Mon, 8 Mar 2010 14:44:34 -0800 [thread overview]
Message-ID: <b41005391003081444r33faed3dy9b2e7e3dcf9edd76@mail.gmail.com> (raw)
In-Reply-To: <1268088000.10198.20.camel@lillen>
Hehe,
http://dev.gentoo.org/~antarus/essays/mixin-profiles.txt
-rw-r--r-- 1 antarus users 2653 Jun 4 2006 mixin-profiles.txt
-A
On Mon, Mar 8, 2010 at 2:40 PM, Peter Hjalmarsson <xake@rymdraket.net> wrote:
> mån 2010-03-08 klockan 19:13 +0200 skrev Mart Raudsepp:
>
>> Instead I think we should be improving "eselect profile" to support
>> multiple inheriting /etc/make.profile files in a user friendly fashion,
>> and in the end removing 249 subprofiles, instead of adding 28+.
>>
>
>
> I vote for this one. A profile being a only contains what is interesting
> for that profile, and you can "stash together" some profiles into your
> own cocktail.
> Yeah, I know it sounds horrible, but it would still be better then to
> only be able to focus on one small set.
>
> For example if I am using the GNOME DE, and have someone other also
> using my computer, but who really wants to use KDE. Should I have to
> find out what from the KDE profile to enable in my env to make my
> GNOME-profile also tingle for KDE?
>
> I think having a set of "base profiles" for toolchains and alike (i.e.
> default, hardened) would be good. Then be able to add for example
> desktop/gnome or server and/or selinux profiles on top would be
> interesting. This also for maintainers, as for example PeBenito can
> focus on the selinux part of the profiles, and do not have to keep up to
> date with which hardened-compilers are currently masked/unmasked.
>
>
>
>
next prev parent reply other threads:[~2010-03-08 22:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 14:52 [gentoo-dev] Split desktop profile patches & news item for review Theo Chatzimichos
2010-03-04 15:29 ` Jeremy Olexa
2010-03-04 17:22 ` [gentoo-dev] " Duncan
2010-03-04 17:59 ` [gentoo-dev] " Sebastian Pipping
2010-03-04 18:15 ` Samuli Suominen
2010-03-04 22:36 ` Ben de Groot
2010-03-05 8:28 ` Joshua Saddler
2010-03-05 12:57 ` Ben de Groot
2010-03-05 13:46 ` Theo Chatzimichos
2010-03-05 17:59 ` Zeerak Mustafa Waseem
2010-03-05 19:01 ` [gentoo-dev] " Duncan
2010-03-05 19:11 ` Theo Chatzimichos
2010-03-05 19:24 ` Zeerak Mustafa Waseem
2010-03-05 19:12 ` [gentoo-dev] " Mike Frysinger
2010-03-08 1:17 ` [gentoo-dev] " Theo Chatzimichos
2010-03-11 1:36 ` Ben de Groot
2010-03-11 20:20 ` Mart Raudsepp
2010-03-11 22:20 ` Ben de Groot
2010-03-12 8:36 ` Mart Raudsepp
2010-03-12 9:48 ` Theo Chatzimichos
2010-03-12 17:39 ` Ben de Groot
2010-03-13 10:07 ` Theo Chatzimichos
2010-03-13 23:37 ` Mart Raudsepp
2010-03-12 15:47 ` Ben de Groot
2010-03-12 17:34 ` Duncan
2010-03-13 23:25 ` Mart Raudsepp
2010-03-23 14:29 ` Theo Chatzimichos
2010-03-08 17:13 ` [gentoo-dev] Reorganizing handling of target specific profiles (Was: Split desktop profile patches & news item for review) Mart Raudsepp
2010-03-08 22:40 ` [gentoo-dev] " Peter Hjalmarsson
2010-03-08 22:44 ` Alec Warner [this message]
2010-03-13 21:16 ` Brian Harring
2010-03-14 0:02 ` Mart Raudsepp
2010-03-14 5:25 ` Brian Harring
2010-03-09 1:26 ` [gentoo-dev] " Robin H. Johnson
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=b41005391003081444r33faed3dy9b2e7e3dcf9edd76@mail.gmail.com \
--to=antarus@gentoo.org \
--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