From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New 10.0 profiles are in repository
Date: Fri, 07 Aug 2009 01:52:37 -0700 [thread overview]
Message-ID: <4A7BEB55.1030601@gentoo.org> (raw)
In-Reply-To: <4A7BE79B.7040105@allenjb.me.uk>
AllenJB wrote:
> Josh Saddler wrote:
>> Mart Raudsepp wrote:
>>> I wanted to work at some point on splitting out gnome and kde profiles
>>> to separate ones. Perhaps desktop profile could be a generic universal
>>> one with USE flags enabled that rox/lxde/fluxbox and so on would like as
>>> well, and then gnome adds its stuff, and kde adds its own stuff.
>>> Or desktop could be one that enabled both GNOME and KDE stuff as now, by
>>> multi-inheriting both gnome and kde profiles.
>>> Or perhaps both a lowest common denominator desktop-base profile and a
>>> big desktop one enabling everything...
>> What could be nice is if users could select multiple profiles. They
>> first choose the "desktop" profile, which has lots of basic stuff that's
>> DE/WM-agnostic. They could then select another profile that adds e.g.
>> Gnome stuff, like you suggested.
>>
>> I suppose the potential problem here (besides coding support for more
>> than one profile) is making sure that the selected profile's USE flags
>> (etc.) don't conflict with other selected profiles. Profile authors
>> would have to be pretty aware of what other profiles contain, and/or the
>> package manager would have to have some heavy duty resolver.
>>
>> One could just avoid the whole multiple-profiles-selected thing by
>> cloning bits of one profile (like a minimal agnostic "desktop"), then
>> adding your own USE flags, and calling it the "Gnome" profile, but this
>> introduces lots of code duplication.
>>
> Many new users seem to have trouble grasping how profiles work in their
> current, relatively simple, format. I think adding complexity to this is
> only going to make things worse.
>
> This will also take a step back in that users will have to be exposed to
> the raw profile locations within the tree. We've only just got rid of
> this (as soon as the handbooks actually get updated, anyway) now that
> "eselect profile" is available in stage3. Getting profile paths wrong
> was, in my experience, one of the most common problems new users had.
The make.profile symlink will still be supported. It's needed at
least for backward compatibility.
> I believe that if you want to successfully implement this idea, you will
> have to create a tool (or modify "eselect profile") to allow this to be
> done without exposing users to the raw paths.
Sure, we can do that.
> AllenJB
>
--
Thanks,
Zac
prev parent reply other threads:[~2009-08-07 8:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 8:19 [gentoo-dev] New 10.0 profiles are in repository Samuli Suominen
2009-08-06 13:13 ` Jeremy Olexa
2009-08-06 14:19 ` Samuli Suominen
2009-08-06 16:51 ` Mart Raudsepp
2009-08-06 18:39 ` Josh Saddler
2009-08-06 19:17 ` Zac Medico
2009-08-07 0:50 ` Alex Alexander
2009-08-07 8:36 ` AllenJB
2009-08-07 8:52 ` Zac Medico [this message]
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=4A7BEB55.1030601@gentoo.org \
--to=zmedico@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