erland wrote: > You are probably already aware of this, but what we should do is to make > it possible for us to override maxVersion in the build script. > > As an example, if I've specified 7.* for a plugin, we should make it > possible to change this to 7.5.* in the build script if the plugin > doesn't work in 7.6.0 and later versions. A plugin can have multiple > entries so we need to ensure to only change the incorrect entry. > > There are still people using 7.5.x version of LMS and we should make > sure the plugin is still available to these users. > > If I remember correctly the plugin installer was added in one of the 7.x > versions so we probably don't have to care about 6.x releases. > > However, a start would be that people in the community report exactly > which plugins that doesn't work, if we are lucky there are just a few of > them and the developers might still be able to adjust their repository > file and then we don't have to do anything in the LMS core.
If we play with the repo build script then I think we should consider a couple of other things: 1) should we just have a repo.xml and get rid of the other.xml (i.e. get rid of the idea of recommended and non recommended plugins?) 2) should continue to be hosted on mysqueezebox.com? We could always host a mirror elsewhere and include the link to that in the server release? [the code will cope with a newer version overriding an older one] For the build script - do we want to override maxVersion by exception? Also do we want to validate if all repos are really contributing working plugins? ------------------------------------------------------------------------ Triode's Profile: http://forums.slimdevices.com/member.php?userid=17 View this thread: http://forums.slimdevices.com/showthread.php?t=101265 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
