Am 23.06.2009 19:52, schrieb Stephan Raue:
> Am 23.06.2009 16:40, schrieb Olivier Tilloy:
>
>> Yes, letting the packagers decide where to install system-wide plugins
>> makes sense (as long as it's not in the pythonpath but in a dedicated
>> directory). But that means moovida needs to be informed of the path
>> where these plugins are installed at startup. Is there any standard
>> mechanism for this? Let the packages hardcode this path in the launcher
>> when installing the plugins maybe?
>>
>>
>>
> we can use a configfile that moovida reads in pythonpath (moovida-dir)
> not for change by users (or only experts) or setup.py hardcode this dirs
> to launcher, i would prefer the option for more that one location (eg
> setup.py --plugindir="/dir1,/dir2,..." so we have the option to install
> plugins systemwide and for an user only (moovida searches in the order
> how its set-up with the option plugindir)
>
> Stephan
>
>
with another options in a seperate configfile the packagers can easyly
disable autoupdate of plugins and switch of all plugin (install) stuff
(and the plugin menu) - this is a different enhancement for packagers
Stephan
--
### OpenELEC.tv ###
The free and open Mediacenter Distribution 4 you
http://www.openelec.tv
