Quoting Dan Sully <[EMAIL PROTECTED]>:
What is Slimdevices policy on hosting 3rd party software ?
Depends on what it is.. generally we don't.
Better that way, I think. Some plugins keep pace with slimserver,
others don't. Some downright fall right out of maintenance. The API
can't stay stagnant simply becuase of the high level of interraction
that plugins are allowed and the features that users want from
slimserver itself. Maintenance/QA of SD hosted third party plugins
has the potential of becoming a real problem.
it might be an interim step to add requirements to a plugin to have
the following addition info available:
version number: plugin version tracking
download url: last valid location for updated versions or home page
for grabbing new modules.
compatibility level: slimserver version required/to be installed on.
This way, any server install could eventually automatically disable
plugins that don't match teh server version on compatbility, report an
existing version number compared to something that could be returned
from the download url. Minimally, the server could have a page that
lists third party plugins, with links, suggesting an update. Then a
button at the bottom to bypass end re-enable the plugins (hopefully
after the user has updated or removed potentially incompatible plugins)
-kdf
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/unix
