git describe tags returns wrong version about libelektra HOT 7 CLOSED

if add "-DBUILD_TESTING=OFF" fail, without this build OK

from libelektra.

I can confirm your findings. Building with BUILD_TESTING=OFF will fail as the new cmake target cframework won't get defined.

from libelektra.

Thank you for reporting the issue!

I'll fix the build issue and create a new build job on http://build.libelektra.org:8080 so that all variations of enable/disable things are tested.

git describe --long --tags outputs 0.8.1 because this was the last release before we switched to a dedicated "release" branch.

$ git checkout release
$ git describe --long --tags
0.8.8-0-g121407e

Do you think it is more intuitive if master is tagged before it is merged to release?

from libelektra.

I think 'release' branch is redundant, because exist the tags, you can chekout the tag with

git checkout 8.8.0

'master' is for newer commits, include tags

example:

8.1.0 -> tag/release in 'master'
8.1.0.xxxx -> comits after 8.1.0.0 tag/release in 'master'
---- snip ----
8.8.0 -> tag/release
8.8.0.xxxx -> commits after 8.8.0 tag/release in master

greetings

from libelektra.

The idea of the release branch was to have a clean git log for releases only. Additionally, it is used for git buildpackage. Actually some things (e.g. the release and some things on the build server) would be easier with a single-branch (= one master + many feature branches) development.

http://build.libelektra.org:8080/job/elektra-multiconfig-gcc47-cmake-options/
currently builds all combinations of flags and it seems that quite a lot of combinations are broken.
So we definitely need to have some refactoring for the CMake commandline options.
I opened the new issue #111 for that.

So this issue is now for the release branch issue only.

best regards,
Markus

from libelektra.

Note: git build-package must continue to work
update doc/todo/RELEASE

from libelektra.

Problem should be fixed with 0.8.9 release.

from libelektra.