Another reason I see is for ensure visibility of all the modules included. Github projects and subprojects will do the trick very well, but, as we have said, for now we are tied to Launchpad and its constraints (and also its advantages).
Regards. 2013/11/8 Alexandre Fayolle <[email protected]> > On 08/11/2013 13:11, Eric Caudal wrote: > > For my understanding, what is the reason today to have one branch with > several modules? > is it historical or is there a technical/practical reason? > > > The main reason I see with 1 branch with several module is that OpenERP > does not support versionned dependencies, so there is no way to tell that > module1 depends on version >= A.B.C of module2. Having both modules in the > same branch helps ensure that when you check out the branch you get > compatible versions of the modules. > > > -- > Alexandre Fayolle > Chef de Projet > Tel : + 33 (0)4 79 26 57 94 > > Camptocamp France SAS > Savoie Technolac, BP 352 > 73377 Le Bourget du Lac Cedexhttp://www.camptocamp.com > > > _______________________________________________ > Mailing list: https://launchpad.net/~openerp-community > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openerp-community > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
