Mailinglist Archive: opensuse-packaging (134 mails)

[Robert Schweikert <rjschwei@xxxxxxxx>]

On 07/11/2011 11:00 AM, Andreas Jaeger wrote:
> On Monday, July 11, 2011 16:50:57 Robert Schweikert wrote:
> > Understood, but I think at least some of the things that were proposed
> > in this thread (although I am not sure we reached agreement on the
> > preferred way) are not possible with the upstream
> > proposal/implementation. Therefore, we should get a consensus on what we
> > would prefer for openSUSE, if that preferred method is not possible in
> > the current systemd implementation someone (possibly AJ) should take our
> > concerns back upstream and get feedback.
>
> Robert, in this case I missed something. I haven't seen anything that could
> not be done with the proposal from upstream - what I noticed were some open
> questions on how things get done and some alternative proposals where I did
> not see any advantages to the proposal.


My understanding is that the current upstream proposal/implementation 
handles the following case:

Multiple files in /etc/systemd/system.preset and 
/lib/systemd/system.preset each file would be parsed and the expected 
content is:

<snip>
disable avahi-daemon.service
enable cups.service
disable *
</snip>

From original post: 
http://lists.opensuse.org/opensuse-packaging/2011-07/msg00030.html

Then I made two proposal, although I more or less talked myself out of 
one of them in: 
http://lists.opensuse.org/opensuse-packaging/2011-07/msg00041.html

Proposal 1: Have one file per service with the content of enable/disable 
as appropriate, this makes a "disable all by default" policy tedious to 
implement.

Proposal 2: Allow only 2 files, enable.preset and disable.preset each 
file would list the service that is being enabled or disabled.

In http://lists.opensuse.org/opensuse-packaging/2011-07/msg00043.html 
Patrick proposed that there would only be one file that lists all 
services and enables/disables them.

Proposal 3: Only one file (decide on name) is supported to 
enable/disable services

In http://lists.opensuse.org/opensuse-packaging/2011-07/msg00053.html 
Christian proposed to have subdirectories named enable and disable and 
have empty files for each service in the enable or disable subdirectories.

Proposal 4: Create subdirectories enable/disable and have empty files as 
indicators whether a service should be enabled or disabled.

In http://lists.opensuse.org/opensuse-packaging/2011-07/msg00055.html, 
Rob proposed a modified version of proposal 4.


In http://lists.opensuse.org/opensuse-packaging/2011-07/msg00063.html 
you AJ mention that systemd already has an enable directory, something 
that was not part of the original message posted. Based on the original 
message posted it appears to me that upstream modifications would be 
necessary for proposals 2, 3, 4, and 4a. However, the upstream 
implementation my be more flexible than is obvious from the original post.

IMHO we should find consensus for the preferred approach for openSUSE, 
(1, 2, 3, 4, or 4a) and then double check with the capabilities of the 
upstream proposal/implementation.

Thanks,
Robert


--
Robert Schweikert                           MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center                   LINUX
Tech Lead
rjschwei@xxxxxxxx
rschweik@xxxxxxxxxx
781-464-8147
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx