id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
19561	Improve plugin update UX with Debian packages	stanton	stanton	"I use JOSM on Ubuntu, installed via an official deb package.

When a new JOSM build is available, it gets installed as part of my usual update cycle—I usually install package updates as they get available, which happens every other day. Since I trust my package sources, I don’t even realize when JOSM is getting updated at the time I am installing the update.

The next time I start JOSM I them get prompted to update my plugins—pretty much out of the blue, and there is a delay in my workflow.

I understand there is a general issue to be resolved, as the JOSM Debian package installs to shared directories whereas plugins live in the user directory, which Debian install routines are not meant to touch.

I was wondering if this could still be simplified, though:

* JOSM would need to be able to run plugins installed in a specific shared dir (outside the home dir), if that’s not already the case. Users typically won’t have write access, thus these plugins never get updated with the existing plugin update mechanism, and users never get prompted to update them.

* Plugins would need to be debianized (basically porting the existing plugin install routine to deb, probably mostly identical for all plugins) and the debianized versions would install to the shared dir.

* Plugin updates would then be offered through the package update mechanism, no need to prompt for that on startup. The prompt would only appear if JOSM finds plugins in the user dir, and only those would get updated.

* Optionally, the JOSM plugin selector could offer to install plugins for all users (rather than just the current user) and, if that option is selected, call a wrapper around the package manager."	defect	closed	normal		Core		worksforme