Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On the subject of floating tags I could not find an equivalent when we moved to CVSNT either. PVCS has this concept, BTW, and once you get in the habit of floating tags it is very hard to switch out of. Modules do not work well because, well, modules are very complicated. That's why we now have modules2 which is also somewhat complicated. Also, modules are an admin level concept and not an end user tool like tags are. My guess is it would be hard to implement floating tags in CVSNT but I can garauntee there are several development groups migrating from PVCS, at least, that would transition more easily and comfortably if CVSNT had floating tags as well. I think this would be hard mostly for CVS cultural reasons - you don't often set a tag to a specific file revision in CVSNT explicitly but under PVCS we did this a lot. Having said all that, the way we deal with grouping files together for distribution is packaging scripts that run by hand or during nighly builds. These run over a checked out sandbox of any branch and collect up a seperate copy of each file in whatever new directory tree is required by the package recipient. This forces us to make mods to the scripts for each file add/remove on each branch instead of a floating tag simply following the revision line for each file but at least it puts control back in the developer side of the fence. HTH, Aric Aric Czarnowski Unimax Systems Corporation 612-204-3634