On 2014-02-19 2:04 AM, Daniel Campbell <li...@sporkbox.us> wrote:
For such a profile to be legitimate, systemd would have to be chosen as
the default.
Ridiculous. Forget about Canek's rant...
This is about *choice*. Also, I would argue the *opposite of what Canek
is saying in this last rant...
If he and other want systemd profiles, let *them* do the work of
creating and maintaining them.
All the Gentoo Council would have to do is make this a new rule or part
of the Gentoo Constitution or whatever guidelines govern things like this:
"In keeping with Gentoo's Official Policy of providing maximum choice to
its user base, we hereby authorize this formal process for nominating,
creating, and maintaining new profiles that make use of the new systemd
init system."
And the number of profiles wouldn't even quite double. There are 16 now,
if each and every one had a systemd counter-part, it would add 12 more.
So, as systemd users create the new profiles, instead of:
# 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
we may eventually (at worst) end up with:
# eselect profile list
Available profile symlink targets:
[1] default/linux/amd64/13.0 *
[2] default/linux/amd64/13.0/systemd
[3] default/linux/amd64/13.0/selinux
[4] default/linux/amd64/13.0/selinux/systemd
[5] default/linux/amd64/13.0/desktop
[6] default/linux/amd64/13.0/desktop/systemd
[7] default/linux/amd64/13.0/desktop/gnome
[8] default/linux/amd64/13.0/desktop/gnome/systemd
[9] default/linux/amd64/13.0/desktop/kde
[10] default/linux/amd64/13.0/desktop/kde/systemd
[11] default/linux/amd64/13.0/developer
[12] default/linux/amd64/13.0/developer/systemd
[13] default/linux/amd64/13.0/no-multilib
[14] default/linux/amd64/13.0/no-multilib/systemd
[15] default/linux/amd64/13.0/x32
[16] default/linux/amd64/13.0/x32/systemd
[17] hardened/linux/amd64
[18] hardened/linux/amd64/systemd
[19] hardened/linux/amd64/selinux
[20] hardened/linux/amd64/selinux/system
[21] hardened/linux/amd64/no-multilib
[22] hardened/linux/amd64/no-multilib/systemd
[23] hardened/linux/amd64/no-multilib/selinux
[24] hardened/linux/amd64/no-multilib/selinux/systemd
[25] hardened/linux/amd64/x32
[26] hardened/linux/amd64/x32/systemd
[27] hardened/linux/uclibc/amd64
[28] hardened/linux/uclibc/amd64/systemd
You would also have to require package maintainers to support both
profiles, unless the upstream package itself changed such that it would
no longer work without systemd.
