On 10/11/2011 16.41, Cyril Hrubis wrote: >>> Hmm, that wouldn't work for released tarbals that are shipped without >>> the .git/ directory. We need to look if there is a git repository first >>> and then decide to use VERSION or git describe. I'll fix these soon. >>> >> >> I was proposing to create the VERSION from the git in the install >> step, and then package it with the released tarball (out of git). > > Hmm, that creates a chicken and egg problem. The commit that changes > VERSION file content is then tagged with the new version tag. Or did I > misunderstand you? >
probably. I do no intend to have VERSION under SCM, no sense to me if we have LTP properly tagged. SO, for example, as soon we tag LTP-20111201 (i.e. december release), the 'install' make file target will create a VERSION file to be packaged, but VERSION will be a private file, never committed on git. cheers ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
