[gentoo-dev] [RFC] Global USE=systemd

[gentoo-dev] [RFC] Global USE=systemd

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 2549 bytes --]

A growing number of packages use USE=systemd in a semi-controlled way.
Therefore, I suggest establishing a global flag described as:

systemd - Enable use of systemd-specific libraries and services like
  socket activation or session tracking

$ quse -D systemd
 local:systemd:app-admin/openrc-settingsd: Use the versions of dbus and polkit files provided by sys-apps/systemd
 local:systemd:app-emulation/qemu-guest-agent: Install SystemD init script instead of OpenRC
 local:systemd:gnome-base/gdm: Use sys-apps/systemd for session tracking
 local:systemd:gnome-base/gnome-control-center: Use sys-apps/systemd instead of sys-auth/consolekit for session tracking
 local:systemd:gnome-base/gnome-session: Use sys-apps/systemd instead of sys-auth/consolekit for session tracking
 local:systemd:gnome-base/gnome-settings-daemon: Use sys-apps/systemd instead of sys-auth/consolekit for session tracking
 local:systemd:gnome-base/gnome-shell: Use sys-apps/systemd instead of sys-auth/consolekit for session tracking
 local:systemd:gnome-base/gvfs: Use sys-apps/systemd seat information for tracking owners of removable volumes
 local:systemd:gnome-extra/gnome-packagekit: Use sys-apps/systemd instead of sys-auth/consolekit for rebooting
 local:systemd:gnome-extra/gnome-screensaver: Support sys-apps/systemd's logind
 local:systemd:gnome-extra/gnome-system-monitor: Display sys-apps/systemd metadata, e.g. unit names, for running processes
 local:systemd:media-sound/mpd: Enable support for systemd socket activation
 local:systemd:media-sound/pulseaudio: Build with sys-apps/systemd support to replace standalone ConsoleKit.
 local:systemd:net-misc/networkmanager: Use sys-apps/systemd instead of sys-auth/consolekit for session tracking
 local:systemd:net-print/cups: Add support for systemd socket activation.
 local:systemd:sys-apps/accountsservice: Use sys-apps/systemd instead of sys-auth/consolekit for session tracking
 local:systemd:sys-apps/busybox: Support systemd
 local:systemd:sys-apps/dbus: Build with sys-apps/systemd at_console support
 local:systemd:sys-apps/udevil: Support for sys-apps/systemd
 local:systemd:sys-auth/pambase: Use pam_systemd module to register user sessions in the systemd control group hierarchy.
 local:systemd:sys-auth/polkit: Use sys-apps/systemd instead of sys-auth/consolekit for session tracking
 local:systemd:sys-fs/udisks: Support sys-apps/systemd's logind
 local:systemd:sys-power/upower: Use sys-apps/systemd for hibernate and suspend

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

Re: [gentoo-dev] [RFC] Global USE=systemd

[Tomáš Chvátal]

Does it really have to be useflag? Can't we simply just install the
file every time like we do with everything else? Logrotate/normal
initscripts/etc/etc.

There should be no issue with that if we install the service files
every time, they just take few kbs in /etc/

Re: [gentoo-dev] [RFC] Global USE=systemd

[Rich Freeman]

On Sat, Dec 8, 2012 at 8:53 AM, Tomáš Chvátal <tomas.chvatal@gmail.com> wrote:
> Does it really have to be useflag? Can't we simply just install the
> file every time like we do with everything else? Logrotate/normal
> initscripts/etc/etc.
>
> There should be no issue with that if we install the service files
> every time, they just take few kbs in /etc/

For unit files I'd tend to agree.

However, these did not control the installation of unit files (unless
I missed something in there).  Many controlled whether the package
used consolekit vs systemd, so unless somebody defines a common API
between them and a virtual a USE flag makes sense.

I'm not as certain about the socket file use case.  If the use flag is
triggering both the installation of a socket file and also the
disabling of something else it might be necessary.  On the other hand,
if it is just toggling between installing the socket file for systemd
vs under xinetd.d then it might be safe to just install both since I
doubt systemd users are likely to also run xinetd. That might not be a
safe assumption - during the transition they might end up running
both.

Re: [gentoo-dev] [RFC] Global USE=systemd

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 646 bytes --]

On Sat, 8 Dec 2012 14:53:02 +0100
Tomáš Chvátal <tomas.chvatal@gmail.com> wrote:

> Does it really have to be useflag? Can't we simply just install the
> file every time like we do with everything else? Logrotate/normal
> initscripts/etc/etc.
> 
> There should be no issue with that if we install the service files
> every time, they just take few kbs in /etc/

It's not about unit files. For those, I tend to kill people for putting
them behind a flag.

This is mostly about:

a) using logind instead of consolekit,

b) linking programs against systemd libraries (hard dep on systemd).

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]