Autoupdate of java application downloads external libraries
Hello mentors,
I'm currently packaging the application jDownloader which requires very
frequent updates. The mainstream devs have solved the updating with an
auto-update feature that checks for new versions of the core part and
plugins. As I understand, this is absolutely ok as other applications
(like Iceweasel) do the same for their plugins. The problem now is, that
the auto updater also updates some internally used java libraries which
are also available in the debian archives. For example, the application
depends on libswingx, but instead of using the system wide installation
it uses a local version that is retrieved with the auto updater.
Now my question is: Is this ok for Debian? Is it ok to ignore installed
libraries and use local versions instead? Also, is it generally ok if an
application is able to update it's own core (not only plugins)?
I really would like to change the source so that it uses the installed
libraries instead. But the problem is that the auto update process may
add/remove/change dependencies and I don't see a way to handle that.
Btw, the auto updater is absolutely required. jDownloader is based on a
lot of plugins which are for example responsible for link extraction
from external sites. Everytime one site changes something, an update is
required to make the plugin work again.
Thanks,
Alex
Reply to: