I assume you build within the source tree. Prefer VPATH-builds
and the issue of overwritten *.1 and *.info files will go away.
The version labeling, e.g. "enblend-4.1-123deadbeef", is completely
intentional; it distinguishes and (almost) uniquely identifies
development versions. If you are fed up with it edit the file
"VERSION" in the project's root directory, set any version code you
want, re-generate the configuration files, and rebuild. BTW, this will
definitely happen when we shall prepare the next release. We shall
run through
enblend-4.1rc1,
enblend-4.1rc2,
enblend-4.1rc3,
...,
and finally
enblend-4.1.
I assume you build within the source tree. Prefer VPATH-builds
and the issue of overwritten *.1 and *.info files will go away.
The version labeling, e.g. "enblend- 4.1-123deadbeef ", is completely
intentional; it distinguishes and (almost) uniquely identifies
development versions. If you are fed up with it edit the file
"VERSION" in the project's root directory, set any version code you
want, re-generate the configuration files, and rebuild. BTW, this will
definitely happen when we shall prepare the next release. We shall
run through
enblend-4.1rc1,
enblend-4.1rc2,
enblend-4.1rc3,
...,
and finally
enblend-4.1.