Re-starting daemons across upgrades? (was: Thank you (for making the ports less boring).)

[Matthias Andree]

Am 16.09.2011 11:51, schrieb Lev Serebryakov:
> Hello, Freebsd-ports.
> You wrote 16 сентября 2011 г., 0:28:07:
> 
>>> Really? I thought it was supposed to be standard behaviour- the @stopdaemon
>>> line in pkg-plist facilitates that.
> 
>> While I totally understand why we do this, I have to say it's VERY
>> VERY annoying behavior especially when one upgrading a remote system
>> with multiple server daemon ports.  One have to watch the whole
>> process carefully and restart the daemon manually.
>   Yep, and even more annoyingly is that it is completely inconsistent:
>  some daemons are stopped, some not, etc.

We do not currently have a standard procedure for that, nor do we record
the necessary state -- perhaps we should just discuss, vote, and add a
paragraph to the porter's handbook.

We also need to bring the authors (or volunteers) for the de-facto
standard upgrade tools into the loop.

My thoughts:

- give the user a choice to configure whether to restart services

- optional: give the users a chance to configure this per-service

- discuss whether we want/need to support this (a) in the framework that
we currently use, (b) only in pkgng, (c) in portmaster and portupgrade
where necessary.