NFD » ndn-tools

We need some form of the release, otherwise I don't even know which version to assign for the packaged versions.

The embedded tools in ndn-tools are no longer completely independent and no longer have their independent versioning.

I don't even know which version to assign for the packaged versions.

An easy choice is to use "0.0.0" plus the commit hash.

A prior example is NLSR 0.2.0-5-gcae33b6-ppa1~trusty.

In any case, we need some release for tools.

Please explain the necessity. Formerly, neither ndn-tlv-ping nor ndndump had any release.

ndndump had multiple releases. ndn-tlv-ping was never released, but it is project's problem.

The version needed to work as a checkpoint. Without having at least one base release, the git-based versioning does not work: it needs a base tag.

As of right now, the non-existing versioning is a mess. All apps returning 0.1.0-dev, which does not correspond to PPA version and does not have any relation to git commit.

Reply to note-6:

It's unnecessary to have base tag.

shijunxiao@m0212:~/ndn-tools$ echo '0.0.0-'$(git describe --always)
0.0.0-efa3557

Alternatively, use the date of latest commit.

Swarm for Android is known to use such version numbers.

shijunxiao@m0212:~/ndn-tools$ php -r 'echo date("Y.m.d",strtotime(str_replace("Date:","",$argv[1])));' "$(git log | grep Date | head -1)"
2015.06.22