Skip to content
This repository has been archived by the owner on Apr 9, 2019. It is now read-only.

Consider using tagged version #1

Closed
rraptorr opened this issue Jan 17, 2012 · 2 comments
Closed

Consider using tagged version #1

rraptorr opened this issue Jan 17, 2012 · 2 comments

Comments

@rraptorr
Copy link

Hi,
please consider using tagged version of my Java packaging script:

  • that way you can have repeatable builds (master branch changes, so the builds created at different times can be slightly different)
  • from time to time I can break something in master, using tagged version will make your script work regardless of any breakage in master

You can either hardcode the tag you want to use (like v6.30-2) or use something like this to detect newest version:

TAG=`git tag -l 'v6.30-*'|tail -n1`
git checkout $TAG
@rraptorr rraptorr reopened this Jan 17, 2012
@rraptorr
Copy link
Author

Sorry, wrong button clicked;)

@flexiondotorg
Copy link
Owner

Hi!

Thanks for your great packaging work, without which my script would not exist. I had already considered linking to a tag or revision. I've just committed a version which uses tags. I've also seen your 'oracle-java7' stuff and intend to integrate with that too in the future ;-)

Regards.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants