View previous topic :: View next topic |
Author |
Message |
ShanaXXII Apprentice
Joined: 29 Jun 2014 Posts: 283 Location: Canada
|
Posted: Fri Sep 12, 2014 1:19 am Post subject: Systemd without gnome/kde? > eselect profile list |
|
|
Is it possible to install systemd without having to use gnome or kde profiles?
Because in my profile list, there are only kde and gnome that have systemd. Code: | # eselect profile list
[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/musl/amd64
[17] default/linux/uclibc/amd64
[18] hardened/linux/uclibc/amd64 |
|
|
Back to top |
|
|
Jaglover Watchman
Joined: 29 May 2005 Posts: 8291 Location: Saint Amant, Acadiana
|
|
Back to top |
|
|
The Doctor Moderator
Joined: 27 Jul 2010 Posts: 2678
|
Posted: Fri Sep 12, 2014 4:02 am Post subject: |
|
|
I'd add that the only profiles that are really important are the selinux and nomultilib ones. You can craft your settings to suit your needs quite easily on any profile with quite a bit of reading. Basically, all a profile is just a collection of use flags. The exception is that profiles also include masks for certain flags that are unsupported and/or unsafe to use carelessly. This is the reason why the two I listed are special. They are built around forcing certain use that are normally masked.
There is no reason you couldn't set up a desktop using default/linux/amd64/13.0 or a headless openRC server using default/linux/amd64/13.0/desktop/kde/systemd. It is just that doing so would involve changing the flags around. It certainly isn't something you would normally want to do, but you could if you wanted to. _________________ First things first, but not necessarily in that order.
Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box. |
|
Back to top |
|
|
ShanaXXII Apprentice
Joined: 29 Jun 2014 Posts: 283 Location: Canada
|
Posted: Fri Sep 12, 2014 11:25 am Post subject: |
|
|
okay thanks (:
just wondering, if u had a profile with lets say "systemd" and in ur make.conf/package.use u had "-systemd". What would it use? |
|
Back to top |
|
|
depontius Advocate
Joined: 05 May 2004 Posts: 3509
|
Posted: Fri Sep 12, 2014 11:53 am Post subject: |
|
|
Really IMHO the profile tree is set up wrong. The systemd/non-systemd fork should be fairly near the top, just above the server/desktop fork. The gnome/kde fork is under desktop, and putting systemd below that is just too low. Really systemd lies just above the kernel, and that should probably be reflected in the profile paths. I haven't heard about systemd on arm, but I suspect that systemd/non-systemd should really fork even before the machine architecture. _________________ .sigs waste space and bandwidth |
|
Back to top |
|
|
nenemsis5 n00b
Joined: 23 Oct 2007 Posts: 72
|
Posted: Wed Dec 09, 2015 8:37 pm Post subject: |
|
|
i also wonder why we dont have n profile which contains:
desktop + systemd |
|
Back to top |
|
|
|