Hello Olivier, despite being "deprecated" many modules are still only maintained in the "extra addons" branch. For instance some 5 modules required for the Brazilian localization are to be found in that branch (because they could also be used in other state federations, eventually USA or even Europe as a whole), but also many useful modules like product_variant_multi, nan_product_pack...
I insist apps.openerp.com is absolutely not a solution yet as it is. Like if you search for magentoerpconnect you won't find the 6.1 presentation cause it's shadowed by some old certified version, if you search purchase_to_sale, instead of finding my module pruchase_to_sale you'll find dozens of modules dealing with purchase OR sale.... But more importantly, today, because of OpenERP's SA idea of not using any standard package format (like Tryton for instance), we still don't have version dependency management (and please don't try to re-implement it internally, I've seen all the bugs a project like Bundler had, it's not trivial), so maintaining things is hundreds of different branches is absolutely not viable today because you can never know what works with what commit number, there are just too many combinations and fetching all your branches is also tedious and error prone. A better solution would be to have version control dependency. Else, it's still not over at all where modules should be developed/published and given this situation, the extra addons are still being used actively by the last serious guys in the OpenERP ship. I'm a bit afraid you doesn't seem aware of this problem at OpenERP SA... Regards and thanks for all the good work nonetheless. -- Raphaël Valyi Founder and consultant http://twitter.com/rvalyi <http://twitter.com/#!/rvalyi> +55 21 2516 2954 www.akretion.com On Wed, Feb 15, 2012 at 7:56 AM, Olivier Dony (OpenERP) <[email protected]>wrote: > Review: Needs Fixing > > Hi, > > The bzr_set script is kind of deprecated for a few reasons: > - it does not setup shared bzr repositories, hence is not a good way to > initialize a development environment (check out of new branches will be > needlessly slow) > - for production environments it might be workable, but it fetches the > extra-addons branches that are deprecated in favor of OpenERP Apps, > therefore not very useful > > We mention in the 6.1 release note that a new script can be used for > setting up a developer environment: > http://bit.ly/openerp61RN#heading=h.seriyncfihuy > > Nevertheless, thanks for helping maintain bzr_set.py. > > How about making your patch a little bit more generic and already > compatible with the about-to-be-released 6.1 version? You could probably > just test something like version < '6.1' to set the correct path for all > future versions. > This could also be written more concisely: > bzr_links = { 'addons/*': version < '6.1' and 'server/bin/addons' or > 'server/openerp/addons/' } > (or with the Python 2.5 if/else boolean operators) > > Thanks! > -- > > https://code.launchpad.net/~openerp-community/openerp/skitzotek_trunk_symlinks/+merge/93115 > Your team OpenERP Community is subscribed to branch > lp:~openerp-community/openerp/skitzotek_trunk_symlinks. > > _______________________________________________ > Mailing list: https://launchpad.net/~openerp-community > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openerp-community > More help : https://help.launchpad.net/ListHelp > https://code.launchpad.net/~openerp-community/openerp/skitzotek_trunk_symlinks/+merge/93115 Your team OpenERP Community is subscribed to branch lp:~openerp-community/openerp/skitzotek_trunk_symlinks. _______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
