On 2014-02-18 11:39 AM, eroen <er...@falcon.eroen.eu> wrote:
On Tue, 18 Feb 2014 11:24:05 -0500, Tanstaafl
<tansta...@libertytrek.org> wrote:
Hi all,
Ok, before I go and open up a bug requesting this...
I know there have to be a lot of people on this list who can answer
this question...
Is making the use of systemd or not based on a selected Profile, as
opposed to manually trying to do it via USE flags etc, a practical
request, or not?
How is this different from the status quo? There are several systemd
profiles available that make use of the files
in /usr/portage/profiles/targets/systemd/ to make the proper package
settings for using systemd on gentoo. AFAIU, a user should only need to
switch the profile, install and configure systemd itself and configure
their bootloader to start using systemd.
Interesting! I guess it's been a while since I looked at the available
profiles, because I don't remember seeing those:
# eselect profile list
Available profile symlink targets:
[1] default/linux/amd64/13.0 *
[2] default/linux/amd64/13.0/selinux
[3] default/linux/amd64/13.0/desktop
[4] default/linux/amd64/13.0/desktop/gnome
[5] default/linux/amd64/13.0/desktop/gnome/systemd
[6] default/linux/amd64/13.0/desktop/kde
[7] default/linux/amd64/13.0/desktop/kde/systemd
[8] default/linux/amd64/13.0/developer
[9] default/linux/amd64/13.0/no-multilib
[10] default/linux/amd64/13.0/x32
[11] hardened/linux/amd64
[12] hardened/linux/amd64/selinux
[13] hardened/linux/amd64/no-multilib
[14] hardened/linux/amd64/no-multilib/selinux
[15] hardened/linux/amd64/x32
[16] hardened/linux/uclibc/amd64
So, does this mean we will eventually have systemd choices for *all*? Ie:
# eselect profile list
Available profile symlink targets:
[1] default/linux/amd64/13.0 *
[1] default/linux/amd64/13.0/systemd
[2] default/linux/amd64/13.0/selinux
[1] default/linux/amd64/13.0/selinux/systemd
etc?
