Skip to content

Conversation

@kxepal
Copy link
Member

@kxepal kxepal commented Oct 7, 2015

No description provided.

@janl
Copy link
Member

janl commented Oct 7, 2015

+1

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we grab the actual value here? For users of couchdb 2.0, 2.1, etc, they won't see or care about these values, but other users, like Cloudant, will make releases that only change some applications, so showing the actual git value will help. Specifically, the output of git describe --always --tags within that directory.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure. So: ${VERSION}-git describe --always --tags ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hm, I think just the value of git describe --always --tags. the $VERSION value should be in the tarball file name and in the GET / welcome message.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@kxepal
Copy link
Member Author

kxepal commented Oct 7, 2015

@janl @rnewson updated PR with correct vsn fix (:
I don't like set +e set -e around grep ... | xargs sed ..., but didn't found any clever way to not have script fail for apps which already provides not-git vsn. Thoughts?

@rnewson
Copy link
Member

rnewson commented Oct 7, 2015

+1, we can always tidy later when inspiration strikes.

This is what rebar will try to do on make for generated tarball, but
it will because missed .git directories around.
@kxepal
Copy link
Member Author

kxepal commented Oct 7, 2015

Good. Landed. Thanks!

@asfgit asfgit merged commit 9d579fa into apache:master Oct 7, 2015
janl pushed a commit that referenced this pull request Jan 5, 2020
nickva pushed a commit to nickva/couchdb that referenced this pull request Sep 7, 2022
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.

4 participants