Re: Package review and comment wanted
>>> for the buppo --version output. And I think it would be handled by cvs
>> or subversion, but for the moment I am actually using .deb as my
>> revision control....
>
> OK, so you do actually want to have your version information generated
> automatically from your revision control stuff.
:-) That was my idea yes :-) Since I tend to forget this I wanted it to be
automatically.
>
> I use tla for most of my ongoing development work now, and I've put
> scripts
> together to make a release for me. This includes creating a tag branch
> for
> the release, as well as automatically sorting out the version numbers in
> the
> code. (I'm actually basing my versioning off the Debian changelog, since
> it's a Debian-native project, but that's not important). What you could
> do
> is write a script which takes an argument of your new version number,
> which
> tags in your revision control system, does a search-n-replace with sed for
> inserting the current version number, and perhaps resets the debian
> version
> in debian/changelog (run something like dch -v <foo>-1).
I ended up doing something like this in the Makefile.
Taking the version number of the directory name actually, and doing the
sed change in the source file. Just that I do not want to end up doing
serious damage to the file itself.
But I thought that perhaps the debian package building system had some
features for doing this automatically. :-) Ok, I was hoping....
Hmm.. I think perhaps I will simply add a new one line source file in the
etc directory which contains the revision data.
buppo can then source this file, and this makes me feel a lot safer.
> I love shell scripting.
O'h yes... but I have loads to learn...
>
> - Matt
/Bengt
Reply to: