Arthur, > Very oddly this exact same question came up on the TortoiseCVS list > just yesterday about CVSNT...
> There is no automatic way of doing what you want - but you could > use cvs admin to remove the old versions. Yes, I know. I will have to experiment with this. As this feature is described as dangerous in the Cederqvist, I shied. > If you could take some time to explain why your build process would > want to store these files in version control so it can complete the > build process I'd like to know. I have a number of graphics which I create in GIMP, and also save in GIMP file format (.xcf). These files are versioned of course to keep track of what was done. For building my application, I export the graphics manually to PNG. So I have to do this whenever I change the GIMP file. The build process run by ant then includes these PNGs in the output. As long as I work only on 1 machine, no problem: no versioning of the PNGs required. When working on the project on more machines and with more persons, these PNGs have to go into the repository, otherwise everyone has to export them manually whenever the GIMP file changes. But now the repository grows and grows with files that need not to be versioned, just need to be kept for convenience. See? Abstracting: Keeping only latest version is necessary for a product file that requires manual build effort. I could not find the feature in the svn doc either, so this seems to be unique for VSS. Maybe usually only proprietary build processes require manual interaction :-). I'll check the cvs admin thing. Best Joachim -- Joachim Schlosser (The e-mail address is fully repliable.) http://schlosser.info _______________________________________________ Info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
