> The 2.4 branch is cunningly disguised as r_2_3_final. Cool, thanks.
> A fresh source tree is pulled in by packaging/BuildSnapshot.py, which > now has a -t (--tag) option to specify the desired CVS tag. After > that, insert a packaging/linux/debian directory and run packaging/ > BuildSnapshot.py with the --no-checkout option to build from your new > tree. When the packaging/linux/debian/* files are complete (i.e. > correctly build the package), they could go into CVS. Using the > BuildSnapshot.py mechanism takes a bit of work to set up (adapt > fedora, gentoo or slackware directories), but really saves time in > the long run; as changes are made to CVS, new snapshots and point > releases become trivial (sort of, mostly, sometimes,...). That's how the debian packaging currently works, although it still needs some tweaking before being ported into CVS. However I prefer to pull the source first as I need to patch the tree (including the build scripts) to work well with Debian/Ubuntu. Cheers, Steve
