[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How to inform users package is ready to use systemd



Hi,

Thanks all for the ideas in this thread about how to notify users that a
package is ready to be used via systemd service and not used manually.
Some users of simplemonitor missed it and it complicated their lifes.

On 26 Feb 2025 at 10:20:24, Jérémy Lal wrote:
> Le mer. 26 févr. 2025 à 10:09, lorenzo <plorenzo@disroot.org> a écrit :
> 
> > On Wed, 26 Feb 2025 06:37:43 +0100
> > Carles Pina i Estany <carles@pina.cat> wrote:
> >
> > > So I still think that there is room to inform users that a package is
> > > systemd ready and the name of the service and I wondered if there is a
> > > way to do it.
> >
> > then you can use the package description to mention that the package
> > include a simplemonitor systemd service
> >
> 
>  And/or explain what needs to be done to work in README.Debian,
> which is somewhat missing, btw, in the syncthing package.

Since I asked, I saw at least three packages that ask a question in the
postinst via po-debconf. The last one that I see asking this type of
question (I am reviewing/managing some po-debconf translations) is
mopidy. I haven't checked the implementation and wether is a systemd
integration but the question is:

"""
You have the option of starting the Mopidy server automatically on
system boot. If in doubt, it is suggested to not start it automatically
on boot.
"""

So, what do you think if a package asked if you want to enable (default)
or disable being ran from systemd at boot time? (and perhaps show how to
enable/disable/restart at that step?).

It seems that users would not miss it, they can choose, they know, etc.

I wonder why is not more common in the packages carrying systemd
integration. Specially for the ones that are not that clearly a server
(e.g. syncthing might be an example that someone might not expect to be
ran from systemd, probably everyone expects apache/etc.?)

Cheers,

-- 
Carles Pina i Estany
https://carles.pina.cat | carles@pina.cat | cpina@debian.org

Attachment: signature.asc
Description: PGP signature


Reply to: