|
From: | Destailleur Laurent |
Subject: | Re: [Dolibarr-dev] Vagrant box |
Date: | Sat, 1 Nov 2014 21:16:45 +0100 |
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,2014-07-18 10:09 GMT+02:00 Doursenaud, Raphaël <address@hidden>:_______________________________________________2014-07-18 1:17 GMT+02:00 Marcos García <address@hidden>: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 DoursenaudDirecteur technique (CTO)
Dolibarr-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
_______________________________________________
Dolibarr-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
[Prev in Thread] | Current Thread | [Next in Thread] |