Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Derive package build number from number of git commits since last tag #3

Merged
merged 1 commit into from Apr 12, 2019

Conversation

breathe
Copy link
Contributor

@breathe breathe commented Apr 11, 2019

Derive the conda PKG_NUMBER from the number of git commits since the last tag.

You should create a tag somewhere in the repo -- suggest tagging the initial repository commit as '1.1'. The build number will then be the number of commits in the repository since the initial commit -- which is approximately monotonic -- should ensure that libraries which use this package can update to latest build more safely.

When you want to update a project to use updated build of coffee_poisson_solver_ko -- I believe you can just:

conda update coffee_poisson_solver_ko  # update package
conda env export > ...  # keep a shared environment description up to date 

@skw32 skw32 merged commit d25bae2 into skw32:master Apr 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants