On Monday 18 January 2010, you wrote:
> 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.
>
That functionality comes from my 5.0.x hacks. I've been using that one for
quite some time now (also in my 5.1.x branch). Are you sure it had been merged
right in launchpad?
The only quirk, as far as I remember, was that base_module_quality could have
had some bugs with multiple addons paths.
From my conf (all this time):
addons_path = /home/panos/build/openerp/addons/,
/home/panos/build/openerp/addons/etl/lib/, /home/panos/build/openerp/client-
kde/server-modules
See, it takes a comma and a space (did I trim that?) .. Feel free to improve.
On Monday 18 January 2010, you wrote: 'addons_ path'] becomes a list of paths, then 'addons_ path'] + '/' + addon_name`
> Yeah, but if config[
> everything breaks. And even if we keep it as a single string, the addon
> being looked for through `config[
> 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.
>
That functionality comes from my 5.0.x hacks. I've been using that one for
quite some time now (also in my 5.1.x branch). Are you sure it had been merged
right in launchpad?
The only quirk, as far as I remember, was that base_module_quality could have
had some bugs with multiple addons paths.
From my conf (all this time): build/openerp/ addons/ , build/openerp/ addons/ etl/lib/ , /home/panos/ build/openerp/ client-
addons_path = /home/panos/
/home/panos/
kde/server-modules
See, it takes a comma and a space (did I trim that?) .. Feel free to improve.