Basic questions

Owen Taylor otaylor at
Sat Mar 19 22:13:15 UTC 2005

I starting poking around with the extras CVS with a view to maybe
taking over the orphaned fontforge package, and came up with
a few basic questions.

   It looks like there is no tagging of built versions in CVS.  
   If you wanted to reproduce the 0:0.0-2.20041231 build of 
   fontforge, how would you do it? The only tags I see in CVS
   are those from the import script.

   (In the internal Red Hat package CVS, the package maintainer tags,
   then the build system pulls off the tag)


   Once you've updated a package how do you get it built. Is the
   process still "Put a note on or and then magic 

 Releases for different distros

   Say I wanted to update the fontforge package for both the 
   devel branch and for the FC-3 branch. Presumably, I want
   to make sure that the devel version number is always newer
   than the FC-3 version number so that people can do intro-distro
   upgrades and get the rebuilt version. How do I achieve this?

   One system I've used in the past (for Fedora Core / RHEL errata)
   is to say, call the devel version:

   Then backport to FC3 as:

   If I have fix specific to the FC3 package, I might then number 
   the new version as:


   Is it reasonable to do something like this for extras? Is there 
   a standard?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <>

More information about the fedora-extras-list mailing list