question re: best practices,

[Thomas Vander Stichele <thomas urgent rug ac be>]

Hi,

I find myself writing more and more specs for external packages I 
download.  Nowadays I first write the spec before installing stuff ;)
So I also started putting the specs I write in a CVS repository, and I'm 
wondering how other people deal with this sort of thing.

Right now I tend to keep the version number of the original package in the 
spec file name, so that I can backport fixes I make in newer spec file 
updates to older versions of the package in case I still use those.

For example, suppose I package icecast.

I have icecast-1.3.11.spec which I put in cvs.
In the spec file, it has release number 2.
Then 1.3.12 comes out, I copy the previous spec to icecast-1.3.12.spec.
I change the release number to 1.
In this spec file, I also make some sensible fixes that could be useful in 
1.3.11 as well (like, add an init script).
I backport this fix, up the release number for 1.3.11 to 3, and build
both rpms.

(This is only an example, btw ;))

Does it make sense to use the versions in the filename to be able to keep 
track of older packages as well ? What do other packagers do ?

Thanks,
Thomas

-- 

The Dave/Dina Project : future TV today ! - http://davedina.apestaart.org/
<-*-                      -*->
P.S. You rock my world
<-*- thomas@apestaart.org -*->
URGent, the best radio on the Internet - 24/7 ! - http://urgent.rug.ac.be/