Please note that there are two max version settings.
There is maxTarget in the repository files which are used by LMS to show
not yet installed plugins that can be installed, Im for example using
this to distribute multiple TrackStat versions depending which version
of LMS thats used. Any solution in line with this thread needs to make
sure to only ignore maxTarget on the entry with highest maxTarget value,
else you are going to see three different TrackStat versions in the list
and it will be a mess.
In addition to this there is the maxVersion parameter in install.xml
which is used by LMS to decide if it should load a plugin or not. In my
plugins this is set to * since I use the repository files to distribute
the right versions.
All this means that if you want a satisfying solution for my plugins
(which is no longer maintained) the logic needs to rely on the maxTarget
flag in the repository files and not on install.xml, this might
complicate things since Im not really sure the repository files are
used for already installed plugins today.
Instead of adding some complex logic to LMS my suggestion would be:
- For installed plugins: look at install.xml and if maxVersion isnt
compatible dont load the plugin but show it as inactive plugin or
something similar. I think this might be how LMS already is working.
- For plugins not installed: if someone in the community decides that a
plugin works and should be available on a new LMS version even if it
isnt maintained, its easy for someone to provide a new repository file
with minTarget=8.0.0 and maxTarget=8.0.* with a disclaimer in the plugin
description that it isnt supported and might break at any time. You can
also use the creator and email fields to indicate that its not provided
by the original developer.
I dont think it makes sense to spend time to make it easier to install
and use unsupported stuff in LMS when all plugins are open source and
its easy for someone in the community that feels a plugin functionality
is important to take over distribution responsibility by providing a new
repository file. We should encourage the community to take over
maintenance responsibility rather than encourage users to install
unsupported stuff.
Yes, I know Ive had similar ideas as this thread myself and posted
about it in the developers section earlier but Ive changed my mind now
when Ive thought a bit more about it.
Erland Isaksson ('My homepage' (http://erland.isaksson.info))
Developer of 'many plugins/applets'
(https://wiki.slimdevices.com/index.php/User_Erland.html)
------------------------------------------------------------------------
erland's Profile: http://forums.slimdevices.com/member.php?userid=3124
View this thread: http://forums.slimdevices.com/showthread.php?t=113403
_______________________________________________
Squeezecenter mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
