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 Thu, 08 Jul 2004 11:21:40 +0100, Tony Hoyle <tmh at nodomain.org> wrote: >On Tue, 6 Jul 2004 10:41:27 +0200, "Bo Berglund" ><Bo.Berglund at system3r.se> wrote: > >>I am managing a lot of scripted operations on the CVSNT server for building >>our setups. In these scripts I use cvs export a lot to get the files out from >>CVSNT ready to be included into the setup. >> >>I have a slight problem that would be helped if a wildcard specification was >>possible in the commands like: >>cvs export -r HEAD -d DestDir Module/Submodule/supp3-*.cnf > >You can achieve this by creating a module that specifies these files. > >Or use tags - you can tag a directory with wildcards. In both cases it does not help much since I need to get the files by wildcarded names because they will be added by other developers unknown when. So when the script is written the latest such file is available and when the modules file is written the same thing. But if I specify it by name I can only know what is existing *now*. But as soon as someone adds a new file this will not be exported.... As for tagging, if I do this on directory level then I will tag *all* files also those *not* matching the wildcard (i.e. those that I have to somehow exclude from the setup script). So far I see no other route than: - export the whole directory (gets maybe 200 files) - run the del command with wildcards for the *old* files Of course now I have to wildcard removals so I need to know what is common among the files to remove.... /Bo (Bo Berglund, developer in Sweden)