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

Re: Bug#405997: should executables be permitted to update themselves?



On 1/15/07, Michael Gilbert <michael.s.gilbert@gmail.com> wrote:
...
the user did not initiate the action.  azureus went out and checked for
updates, then told the user that they should update.  and it does this every
time the application starts up unless the user chooses to update (at that
point, i don't think it is choice because the user can either say "yes" and
get rid of the annoyance or continue to be annoyed).  i understand that we
should not attempt to limit anyone's freedom of choice, and we are not.  we
are preserving the security, quality, and maintainability of the packages as
distributed and supported by debian.  it is still possible for the user to
choose to download the upstream jar, and run with "java azureus.jar" if they
so choose.  they also have an alternative choice to use the newer azureus
from sid via apt-pinning.  i am not suggesting we prevent either of those
options.

It is only possible for the user to download the upstream jar and run
'java azureus.jar' at the command line if he or she is technically
capable of it. Presenting a technically-more-difficult `alternative'
is no alternative at all. Ditto for the apt-pinning suggestion.

I do agree that it would be better if the update dialog had all three
options `Download update now', `Remind me later' and `Never update'
options. A patch is welcome.

Cheers,
Shaun



Reply to: