Tagging

[rubund]

Can you tag of a release? I'm working on a debian package.

[raboof]

Hello rubund,

Thanks for your interest! Personally I kind of dislike tagging for small projects like this - the current master should always a proper and current version.

I could tag the initial commit '0', then the 'git describe' number of commits since then could be the patchlevel - this way, as suggested in https://github.com/renard/git-deb-pkg, the Debian package version could be something like version '0+git.22-1'.

Would that work for you or would you prefer some other scheme?

Kind regards,

Arnout

[rubund]

Hi Arnout,

I was thinking of a common version name like 0.1.0 or 1.0 or something. But if you don't have any plans of tagging it, it is completely fine, and then I will use the naming convention I've used before for debian packages:
0~20130812git80b1da3-1 for sfarkxtc
and
2.23+20131219gitee08d0c-1 for sfarklib
which will unikely describe the version and sort correctly

It's just that I think it looks a bit more serious when there's a real version number and since you already had tagged of sfarklib sometimes, I thought you wanted to continue with the same.

I've already prepared the package so I'm just waiting for some debian sponsor to get interested and review/upload it.

You may see the packaging here:
git://anonscm.debian.org/pkg-multimedia/sfarkxtc.git and
git://anonscm.debian.org/pkg-multimedia/sfarklib.git

Thanks for your effor putting together sfarklib/xtc. It came in handy for me one day.

Best regards,
Ruben

[rubund]

Another thing is that I can't see your name anywhere in the package. It's a bit sad that you don't get any credit for the work you've done. I could add something to the man-page for sfarkxtc if you agree? But you could also perhaps put a copyright-line for yourself somewhere so that your name will end up in the copyright-file for debian.