Bug#438779: boinc-client: update of package should not start new version automatically
Frank S. Thomas
frank at thomas-alfeld.de
Sun Sep 2 14:59:55 UTC 2007
On Thursday 30 August 2007, Steffen Moeller wrote:
> > On Sunday 19 August 2007, Steffen Moeller wrote:
> > > was preferable to start the client post installation only
> > > * when there was no prior installation of boinc-client
> > > * there was a prior installation and it was running when the update
> > > was initiated.
> [...] It does not resolve the issue of the client starting unasked with a
> first installation [...]
This is a contradiction, isn't it? It _should_ be started unasked with a first
However, you propose to not restart the client on upgrades if it was not
running when the update was initiated. Ok, on upgrades the client is stopped
in the prerm of the old package and started in the postinst of the new
package. How would you know in the postinst then whether the client was
stopped by prerm or it was not running before the upgrade was initiated. For
me it seems that this will add some complexity to the maintainer scripts, but
if you are going to implement this I'm all right with it. :-)
BTW: dh_installinit has the --no-restart-on-upgrade option but this is not
exactly what you want because it will never restart the client on upgrades.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-boinc-devel/attachments/20070902/409163f2/attachment.pgp
More information about the pkg-boinc-devel