Le mardi 12 décembre 2017 à 14:48 +1030, Simon Lees a écrit :
On 12/12/17 08:36, Stefan Seyfried wrote:
Am 11.12.2017 um 22:21 schrieb Dominique Leuenberger / DimStar:
On Mon, 2017-12-11 at 22:02 +0100, Stefan Seyfried wrote:
Still no - the only valid mmethod is to modify systemd- preset- branding- openSUSE
What about systemd-presets-branding-CAASP?
It depends: would you expect bluez to be enabled inside Kubic? (probably not)
Yes. It needs to be enabled always, or it will not work. If is is not enabled, then it cannot be started on-demand by whatever bluetooth applet is installed.
Kubic is this KDE live cd? I think they want to have bluetooth working.
Ah, i see. Kubic is a container.
I would not expect bluez being installed at all in such a hipster-playground ;-)
this is the ONLY package that should bring default states for services for openSUSE.
So who will fix this package?
You can create a submit request for your bits / pieces
And i need to require it from bluez? To make sure that users cannot install What about systemd-presets-branding-CAASP?
Nope - it is, like any other 'branding' package, the DISTROs responsibility to pull in its own branding package. This allows us to use the same RPM (e.g. bluez.rpm) across distros and have various flavors that can decide on their own about what servcies they want/need to enable out of the box.
Yes. But bluez will not work as intended if it is not enabled. (You and Frederic found this out in boo#796671 and opted against presets-branding-openSUSE, because it is not good enough). So the user selects another branding package and -- boom, bluez does not work anymore.
Every other service shipped in openSUSE / SLE is following these guidelines, why should bluez get an exception? You just need to make sure the relevant distro's have the correct services in there branding packages.
The reasoning for bluez, when I fixed it, was it is hardware related and the systemd service will be started by a udev rules, automatically. Unfortunately, to have this working, bluez systemd service needs to be enabled first. But there is nothing really wrong in having it enabled through preset. -- Frederic Crozat Enterprise Desktop Release Manager SUSE -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org