Hi Hideki,

On Wed, Feb 14, 2018 at 11:34:07PM +0900, Hideki Yamane wrote:
> On Sun, 11 Sep 2016 01:59:50 +0200 Ricardo Mones <mo...@debian.org> wrote:
> > > Without disabling auto update check feature, it seems that it is better to
> > > disable auto update check configuration only. attached patch disables it
> > > by default. It makes that user can enable it by clicking manually
> > > configuration option.
> > 
> > If it's better, shouldn't that be done at upstream level?
> > 
> > IMHO all Sylpheed users deserve the same level of goodness, not only the
> > Debian users of Sylpheed, don't they? :)
>  It's good for Debian and other distro package users but not for
>  Windows and binary from source users, since we distro just provide
>  one version for each release.

No, we as distro don't provide just one version: more versions can be
provided through backports. It's just that this had never happened yet
for Sylpheed package because of the lack of manpower and/or interest,
but that could change at some point.

>  Well,
>   - set disable auto update check configuration by default
>   - and for Windows users, install wizard provides enable option
>     for it
>  is best solution, IMO.
>  But I'm not sure whether upstream work on this issue, until then,
>  just specify --disable-updatecheck (and maybe --disable-updatecheckplugin?)
>  for Debian package is simple.

That's too much IMO. If you're going to fix this I think the better is
simply to set the auto-update option to disabled by default, as Kentaro
proposed in his patch.

If you disable the code and somebody wants to enable this feature we'll
be forcing him or her to rebuild from source. If some user wants to know
if a new version is out upstream, even if is using Debian Stable, should
be able to do so in the simplest possible way.

  Ricardo Mones 
  Physics is like sex: sure, it may give some practical results, but 
  that's not why we do it.                            Richard Feynman

Attachment: signature.asc
Description: PGP signature

Reply via email to