Hi Oli, On 03.09.2014 10:51, Oliver Welter wrote: > I would prefer to have an individual branch for each release. The reason > ist, that we need to check in this "special version" file when creating > the tag which will then leed to a wrong version information if somebody > builds from any commit in between two official release points. The idea > on vergen was exactly to prevent this. > > > The layout should look like this: > > * The top commit of the master branch holds the updated VERSION file for > vergen and the official release tag > * A branch named "release/x.x" has one commit on top of this master > holding the persisted version of vergen information. > > This would require, that you tell your build script to pull a special > branch when building. If this is extra work for you, we can also have a > branch "release/current" which always holds the latest pointer.
I can easily cope with any approach. Please choose what is convenient for you. Just ping the list that a new release is ready and where it can be found. But let me recall that this "vergen problem" appeared because github explicitly offers and gives away tarballs without .git subdirectory. Thus anybody (with arbitrary unix, bsd is not specific here) sees such obtained distribution as not working. I mean that personally me is maybe not a proper addressee of these corrections. All the best, Sergei ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ OpenXPKI-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-devel
