PasTim wrote:
> I think some form of warning/information needs to be given somewhow,
> even if just a max version recommendation on the active plugin list.
The problem is that neither maxVersion in install.xml nor maxTarget in
repository.xml can be reliably used for this since different plugin
developers uses them differently. Its also too late to get the
information after LMS have been upgraded because there isnt any easy
way to go back without restoring backups and it wouldnt solve the
scenario when a plugin is incompatible with the new LMS version and
doesnt even load properly.
What you really want is a compatibility matrix which you can check
before upgrading LMS to use as a base for the decision to upgrade LMS or
not. A compatibility matrix could be generated based on repository files
but as mentioned above it really has to be manually updated to be 100%
correct since maxVersion in repository files are used differently by
different developers. However, maybe a generated based on repository
files are better than an outdated manually updated version. A
compatibility matrix doesnt have to be integrated with LMS and doesnt
have to be written in Perl so there is no reason for Michael to spend
time on it, anyone in the community with development skills should be
able to implement one.
I think its time for Michael to get back to implement supported
functionality rather than spend more time to improve stuff related to
unsupported plugins.
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
