Re: Too small permanent file space to co a project
Hello, * On Sat, Dec 11, 2004 at 05:18:12PM +0100 Gerard Cats wrote: Will this work? Yes. Are there things I have to be concerned about, e.g. the administration files in the CVS directories? As long as no CVS watches are set, you do not have any problems. With watches, you will have problems if you overwrite the CVS/ directories with each other, as you will have checkouts then releases. The CVS/ directory is very simple. Just look at the files in there (for example, with less) to see. HTH Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ http://www.viceteam.org/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Too small permanent file space to co a project - again
Thanks, Spiro. With watches, you will have problems if .. OK, I will not use watches. In my proposed method, there are two checkouts, first to $HOME, then to scratch. In one way or another, the second 'cvs co' will need to know what branches/tags the first co referred to. Is there a standard method to accomplish this, or do I have to maintain my own administration file(s) in $HOME for this? ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Too small permanent file space to co a project - again
Hello, * On Sun, Dec 12, 2004 at 04:53:28PM +0100 Gerard Cats wrote: In one way or another, the second 'cvs co' will need to know what branches/tags the first co referred to. Is there a standard method to accomplish this, or do I have to maintain my own administration file(s) in $HOME for this? The file CVS/Tag contains exactly the information you need for this. Just have a look into it. If it does not exist, you have checked out your file without using a tag. Else, it contains Ntag, where tag is the tag used for checking out. HTH, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ http://www.viceteam.org/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Too small permanent file space to co a project
I am looking for help on the following problem: I want to use cvs on a system where the disk allocation on $HOME is too small to check out a project. So I am forced to check out on scratch space. I do not want to edit my files there, because I may lose my work when scratch is cleaned. A possibility is to run cvs co list of files in (a subdirectory) of $HOME, edit the files, and then, in stead of just gmake, run a script that 1) checks out the full project (of the proper branch, tag, etc) on scratch 2) transfers the modified files to that project 3) runs gmake on that project Will this work? Are there things I have to be concerned about, e.g. the administration files in the CVS directories? Thanks. ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
