Comment 5 for bug 507973

> Actually when config['addons_path'] is used in addons it's to physically access to server/bin/addons folder to get ressources, ie access a file within a folder.

Yeah, but if config['addons_path'] becomes a list of paths, then everything breaks. And even if we keep it as a single string, the addon being looked for through `config['addons_path'] + '/' + addon_name` might not be in the folder we randomly selected among all our addon paths. So I really don't think it's acceptable to not fix this.

> For now i don't really know what's the best way but basically we need [...] a method for adding extra addons path on startup (command line) or server config file

I agree, and this method already kind-of exists via ``--addons-path``, it just doesn't work. But before that we need to insulate addons from addons_path.

> I'm gonna make a blueprint to see what other dev thinks.

I wrote a small spec on an API (multiple addons path should be trivial to add once that part's done and folded into trunk + addons), I'm running it before chs and stw to weed out basic stupidity as I'm not a great spec writer, but I should be able to ask you for feedback within a pair of days, if you're interested.