Re: [PATCH v2] systemd: set default.target to multi-user.target

Martin Jansa
2013-01-28T18:43:23Z

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

On Mon, Jan 28, 2013 at 10:44:08AM +0000, Burton, Ross wrote:
> On 25 January 2013 20:26, Martin Jansa <martin.jansa@gmail.com> wrote:
> > ALTERNATIVE_${PN}-systemd = "systemd-def-target"
>
> Let's not introduce packages controlled on distro features whose sole
> purpose is to contain a single file. systemd enabled -> units go into
> $PN.

So I guess upgrade path from meta-systemd won't be ever provided (e.g.
with RPROVIDES/RCONFLICTS/RREPLACES combo).

* check_data_file_clashes: Package dbus-1 wants to install file
* /lib/systemd/system/multi-user.target.wants/dbus.service
But that file is already provided by package * dbus-systemd
* check_data_file_clashes: Package dbus-1 wants to install file
* /lib/systemd/system/dbus.socket
But that file is already provided by package * dbus-systemd
* check_data_file_clashes: Package dbus-1 wants to install file
* /lib/systemd/system/sockets.target.wants/dbus.socket
But that file is already provided by package * dbus-systemd
* check_data_file_clashes: Package dbus-1 wants to install file
* /lib/systemd/system/dbus.target.wants/dbus.socket
But that file is already provided by package * dbus-systemd
* check_data_file_clashes: Package dbus-1 wants to install file
* /lib/systemd/system/dbus.service
But that file is already provided by package * dbus-systemd

> Or, if we accept PN-systemd packages, then I expect to see PN-sysvinit packages.

I wouldn't mind PN-sysvinit, PN-upstart, PN-openrc

It was easy to blacklist sysvinit scripts and then control which packages
should have systemd support just by IMAGE_INSTALL.

Cheers,

--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]