And... What about moving the Vagrant box to an independent dolibarr repo and using relative directories to access the dolibarr code? Like having the following directory tree:
<our dev folder>/dolibarr/ <our dev folder>/dolibarr-vagrant (vagrant will serve ../dolibarr/htdocs files) We are releasing versions with a vagrant box that will stop working in... a month? (because of puppet and repos, updates...) so I think a solution must be found... Regards, *Marcos García* marcos...@gmail.com 2014-07-18 10:09 GMT+02:00 Doursenaud, Raphaël <rdoursen...@gpcsolutions.fr> : > > 2014-07-18 1:17 GMT+02:00 Marcos García <marcos...@gmail.com>: > >> What problems can we have if we use submodules for this? > > They require some specific knowledge that could confuse our contributors. > Also, I'm pretty sure they don't work nicely with egit (Eclipse's git in > java, yuck…) used by some major members of the community. > I use them on one of my modules and they are really tricky to use. > I don't really mind for myself 'cause I know how to use them properly, but > I'm concerned for others. > > Cheers, > -- > *Raphaël Doursenaud* > Directeur technique (CTO) > Expert certifié en déploiement Google Apps > <https://gpcsolutions.fr/raphael-doursenaud-google-apps-certified-deployment-specialist> > +33 (0)5 35 53 97 13 - +33 (0)6 68 48 20 10 > > <http://gpcsolutions.fr> > http://gpcsolutions.fr > Technopole Hélioparc > 2 avenue du Président Pierre Angot > 64053 PAU CEDEX 9 > SARL GPC.solutions au capital de 7 500 € - R.C.S. PAU 528 995 921 > > <https://www.google.com/a/partnersearch/#partner?partner_id=46687933_a0n60000000sqpWAAQ> > <http://wiki.dolibarr.org/index.php/Dolibarr_suppliers_France#GPC.solutions> > > _______________________________________________ > Dolibarr-dev mailing list > Dolibarr-dev@nongnu.org > https://lists.nongnu.org/mailman/listinfo/dolibarr-dev > >
_______________________________________________ Dolibarr-dev mailing list Dolibarr-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
