I am converting from pip/virtualenv to the anaconda science stack and am writing up a conda build install recipe for pyrad since I think that it is relevant to the interests of such folks as that use the anaconda python setup.
I was hoping to take advantage of pulling directly from github, but I need a tag to reference for the pull. I COULD probably just reference a commit ID but I think a tag is cleaner.
TOTALLY understand if you are not ready to call 3.0.6 a "release" but if you are that would be great.
I can alternatively just tag my own fork, but it feels wrong not pointing such an install recipe to the most upstream/author's version.
So I found that this may not be needed after all. It seems I can have it append the hash abbreviation to the package so the version being used is not ambiguous.
Hi man.
I am converting from
pip
/virtualenv
to the anaconda science stack and am writing up aconda build
install recipe forpyrad
since I think that it is relevant to the interests of such folks as that use the anaconda python setup.I was hoping to take advantage of pulling directly from github, but I need a tag to reference for the pull. I COULD probably just reference a commit ID but I think a tag is cleaner.
TOTALLY understand if you are not ready to call 3.0.6 a "release" but if you are that would be great.
I can alternatively just tag my own fork, but it feels wrong not pointing such an install recipe to the most upstream/author's version.
Cheers!
Gus