openerp-community team mailing list archive

[Lorenzo Battistini <lorenzo.battistini@xxxxxxxxxxx>]

On 07/25/2014 12:02 PM, Georges Racinet wrote:
> On 07/25/2014 11:16 AM, Lorenzo Battistini wrote:
> > On 07/25/2014 12:40 AM, Georges Racinet wrote:
> > > Well, would collective.recipe.cmd fit your use-cases enough ? 
> >
> > Hello,
> > we use collective.recipe.patch 
> > <https://pypi.python.org/pypi/collective.recipe.patch> for launchpad 
> > patches (downloaded by the MP diff) and cp.recipe.cmd 
> > <https://pypi.python.org/pypi/cp.recipe.cmd> (collective.recipe.cmd 
> > seems to be better, I didn't know there were several) for github 
> > patches, using hub <https://hub.github.com/> and the command
> > /hub am -3 https://github.com/OCA/web/pull/22/
>
> Interesting, thank you !
> Noticing that git can be aliased to hub and then have a version string 
> that the openerp recipe would not parse (this parsing has been 
> introduced yesterday in trunk version only)

Thanks for the info (and for all your work on the recipe btw ;-) )


> > Commits from 'hub am' are correctly applied because we always specify 
> > the commit hash of every git branch we use.
> in the buildout configuration, I suppose ? 

Yes, something like

version = git https://github.com/odoo/odoo.git odoo 
e80014eae3a622c1491d3f2905b3b6b9e12c6be8


> The freeze and release features would still take the patching as a 
> local modification and refuse to proceed, so I suppose also that you 
> don't use it.

We don't use it.
We fix the environment just using 'versions' for eggs and branches 
revisions (+ possible patches) and putting the .cfg files under VCS


> On a side note, what if the commit you're referring by its hash 
> disappears ?

Uhm, could this happen to stable branches?
If it happens, we will discover it while running the buildout on test 
instances :-)


--
Lorenzo Battistini
Tel (CH): +41 91 210 23 40
Tel (IT): +39 011 198 25481
http://www.agilebg.com
https://github.com/eLBati