public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: systemd as a Profile - practical or not?
Date: Tue, 18 Feb 2014 12:05:37 -0500	[thread overview]
Message-ID: <530392E1.9090906@libertytrek.org> (raw)
In-Reply-To: <20140218173906.25add939@falcon.eroen.eu>

On 2014-02-18 11:39 AM, eroen <eroen@falcon.eroen.eu> wrote:
> On Tue, 18 Feb 2014 11:24:05 -0500, Tanstaafl
> <tanstaafl@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?


  reply	other threads:[~2014-02-18 17:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 16:24 [gentoo-user] systemd as a Profile - practical or not? Tanstaafl
2014-02-18 16:39 ` [gentoo-user] " eroen
2014-02-18 17:05   ` Tanstaafl [this message]
2014-02-18 16:52 ` [gentoo-user] " Canek Peláez Valdés
2014-02-18 17:09 ` Simon László
2014-02-18 17:16   ` Yohan Pereira
2014-02-18 17:29     ` Nilesh Govindrajan
2014-02-18 17:16 ` Nilesh Govindrajan
2014-02-18 17:34 ` Andreas K. Huettel
2014-02-18 23:09 ` Alan McKinnon

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=530392E1.9090906@libertytrek.org \
    --to=tanstaafl@libertytrek.org \
    --cc=gentoo-user@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