CVS Development connected to CVS production
Hi! I was wondering what would be most logical when connecting your developing environment with the production environment. Let's say we have server "developing" which contains a new tagged version ver_2.0 and we want to release everything that is new there to the production environment which is located at another server. How should the root reposistory in the developing be connected to the root repository in the production environment? Can you have clients with the the developing environment as root repository and then view the cvs source at developing as a client to the production environment? In other words, you let the developers commit their changes to the developing cvs, and then, when finished, you tag the developing cvs with a new release number and commits it to the production cvs? Or should the connection be done in another way? Best regards, Patrik ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Modify the export command
Hi! The question: is there a way to exclude certain directories under a module when I make an export on that module? (apart from not tagging that directories, since we want to tag the whole module and all its subdirectories). Can you modify the export command? Background: We will build our developing environment approximately like this: Main_module |__scripts |__docs |__db_files The production environment will have this structure: Main_module |__scripts |__db_files Now, when I make an export to a temporary release directory which I will then tar and send over to the production environment I also get the docs directory, since we tag the whole Main_module. Can you automate the export to exclude certain things? Thanks in advance! /Patrik ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
cvswrapper for binary files
Hi! I will soon make an import of a module that contains some directories with binary files (mostly image files, but also some executables). Does anyone have a good example of a cvswrappers file that I could "steal" so that I don't have to sit and come up with all possible extensions that make up binary files on my own? Yes, I'm lazy :) /Patrik ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
tagging files and certain whole directories in a module
Hi! I want to tag certain files and some whole directories under a module with the same tag. These files will later be exported to a release directory. If I have: Module |_dir1 |_dir2 | |_dir3 How can i tag all files in dir1? The tagging is recursive and will affect dir2 as well, right? /Patrik ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Remove module from Repository and import..
Hi! Can I just remove a module from the repository and then import it again (I have rebuilt the module and there is no one who has begun to develop in the module, so I don't risk losing any history) Regards, Patrik ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Import (first deleting the old Repository source)
Someone please answer this question... Is it ok to just delete (rm -r sourcedir) a cvs source and do a new import with the same vendor tag and release tag with a sligtly modified source (added some directories)? I have also modified my cvswrappers file to treat more extensions as binary since the old import missed some extensions, which is also a reason why I wanna do the import all over again. The question: can i delete the sources from cvs repository and do a new import with the new modified sources, with the same vendor and release tag as the old deleted source? Thanks in advance! /Patrik ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
