Help !!!! - Rights on Branch
Hi All, Please tell me that how can I assign rights to a particular user on selected branches instead of complete repository. Thanks in advance Vijay ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Info about project structuring
Hello, I have been surfing a quite bit to find information about what is important when structuring a project managed in CVS. The project has a pretty clear structure, but I still do not know what these project modules/sub-projects etc. should map to in the CVS world. Example: We can make a project module map to a CVS module. So that we can checkout only that portion of the project, and not bother about the other parts. Also, with the CVSROOT/modules file, we can define entire projects, which checkout all the necessary thigs, enable some level of module bundling. However, the same could be achieved in making it a single CVS module and playing with Makefile/build.xml files to compile/bundle/run only a portion of the whole. Where can I find information about the impact of such decision have on the life of a project ? Proscons, good and bad experiences welcome :-) Thanks, Pascal ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
checkout a deleted tagged file
I have a project within cvs repository. I tagged it and then the project evolved: some files was deleted. When I tried to checkout the tagged version, files deleted was missing although they was present when I tag the project. there is onother way to freeze a version? thanks ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
no space on device - import
Hi, I just had to import (update) a third party source. While importing the import crashed with no space left on device cvs -q import -m Import of NEWVERSION program Manufacturer NEWVERSION [..snip..] N path/subdir/file1 N path/subdir/file2 cvs import: ERROR: cannot write file /home/cvs/REPOSITORY/path/subdir/file3,v: No space left on device cvs [import aborted]: ERROR: out of space - aborting What should I do now to save the situation ? I have tagged the entire tree with the tag before_NEWVERSION. Should I just import cvs -q import -m Import of NEWVERSION program Manufacturer NEWVERSION_FULL after I have made space availible ? and then merge NEWVERSION_FULL and OLDVERSION like usual ? If I have to move the cvs tree (I did not set it up on this device) what do I have to think about ? I will check the faq for this as well. Thank you /Fred ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: checkout a deleted tagged file
From: Massimiliano Cialdi [mailto:[EMAIL PROTECTED]] I have a project within cvs repository. I tagged it and then the project evolved: some files was deleted. When I tried to checkout the tagged version, files deleted was missing although they was present when I tag the project. If the files were deleted with 'cvs rm', there shouldn't be a problem. Are the files in the Attic? If so, are you sure you have the right tag? -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
CVS beginners question regarding simple workflow...
Hi I need some pointers regarding branching versioning. I have created a version of my project, but now I want to fix a bug in the version. I guess I need to create a branch, but am a little unclear on the correct procedure on how to go about it. Could anyone show me a quick recipe on the correct procedure? Anyone? Best regards Lee Francis Is there a FAQ for questions like this? The FAQ's I can find online regarding CVS seem dead/outdated. In theory, there is no difference between theory and practice. But, in practice, there is. -- Jan L.A. van de Snepscheut ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
CVS commit failure and lock files (under windows with cygwin)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am using XP, cygwin, afs, and cvs. Recently I am having problems committing some files. I see from the archives that others have had similar problems, but no solutions have been posted. I try and commit file to repository and get: cvs [commit aborted]: error writing to lock file $repository/,$file, where $repository is the path to the repository and $file is the file I am trying to commit. I have permissions in $repository and can touch ,file, there. But cvs fails. ANy suggestions? - -seth -BEGIN PGP SIGNATURE- Version: 6.5.8ckt http://www.ipgpp.com/ iQA/AwUBPYCG9tqJMFyynoRZEQJQkwCdGnYEv6FMVSigiTWm0kUIcv9tAZsAoLgU qwLVHCl48G1gI38UYylMPV45 =El8b -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: CVS beginners question regarding simple workflow...
I have created a version of my project, but now I want to fix a bug in the version. I guess I need to create a branch, but am a little unclear on the correct procedure on how to go about it. Could anyone show me a quick recipe on the correct procedure? Based on what you described, you shouldn't need to do a branch. Just fix the bug in the appropriate file(s), then re-commit those (files). Is there a FAQ for questions like this? The FAQ's I can find online regarding CVS seem dead/outdated. I agree with your assessment of available FAQs. Most online docs are either technical references, with little explanation of integration into daily practices, or too technically advanced for beginners. To remedy that situation for my own in-house development team, I've started a FAQ of my own. It's not yet ready for prime-time (the section on branches is notably empty), but I add a bit to it each week. You may find it a useful starting point for your learning. http://www.zieg.com/pub/cvs -Mark Zieg ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: CVS beginners question regarding simple workflow...
From: Lee Francis Wilhelmsen [mailto:[EMAIL PROTECTED]] I have created a version of my project, but now I want to fix a bug in the version. I guess I need to create a branch, but am a little unclear on the correct procedure on how to go about it. You can create a branch based on the version tag. See the manual for details: http://www.cvshome.org/docs/manual/cvs_5.html#SEC54 -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: CVS beginners question regarding simple workflow...
From: Zieg, Mark [mailto:[EMAIL PROTECTED]] I have created a version of my project, but now I want to fix a bug in the version. I guess I need to create a branch, but am a little unclear on the correct procedure on how to go about it. Could anyone show me a quick recipe on the correct procedure? Based on what you described, you shouldn't need to do a branch. Just fix the bug in the appropriate file(s), then re-commit those (files). There aren't enough details in the original post to really say one way or the other. If you need to re-release the fixed version and don't mind getting any new commits since the last release, then you don't need a branch. On the other hand, branching lets you fix what's broken without releasing code that may not be ready for prime-time, which is usually what you want. -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
pserver problem
I'm getting the following response when trying to log into my newly created cvs server via pserver: cvs -d :pserver:(user@host):/usr/local/cvsrepos login (Logging in to (user@host)) CVS password: correct password cvs [login aborted]: unrecognized auth response from (host): Unknown command: `pserver' /etc/inetd.conf is configured exactly as it's described in Karl Fogel's CVS book: ... cvspserver stream tcp nowait root/usr/um/bin/cvs cvs --allow-root=/usr/local/cvsrepos pserver ... Hmm, I just noticed that tcpwrappers appear to be in use on this machine. Changing /etc/inetd.conf to cvspserver stream tcp nowait root/usr/sbin/tcpd /usr/um/bin/cvs cvs --allow-root=/usr/local/cvsrepos pserver and... I get a different error: cvs [login aborted]: recv() from server (host): EOF This is running on Solaris 8. Any clues as to why this isn't working, or what I might still have misconfigured? It's the information age --+---+ everything gets saved |UCE/UBE not welcome at this address| except for the human soul.|see http://tinyurl.com/jhb for info| Rev. Matthew Carey, Vision Temple +---+ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
renaming a module
How can I rename a module without loose the files history? thanks ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
moving a file
how can I move a file from a directory to another whithout loose the history? thanks ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Help !!!! - Rights on Branch
Vijay writes: Please tell me that how can I assign rights to a particular user on selected branches instead of complete repository. CVS doesn't really support that directly, but you may be able to use scripts called from the administrative files to do what you want: http://www.cvshome.org/docs/manual/cvs_18.html#SEC156 -Larry Jones Temporary insanity! That's all it was! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: no space on device - import
Fredrik Svensson writes: While importing the import crashed with no space left on device [...] What should I do now to save the situation ? After fixing the space problem, just do exactly the same import again -- CVS will essentially pick up where it left off. If I have to move the cvs tree (I did not set it up on this device) what do I have to think about ? If you can move it without changing its full path and without using symbolic links, the move will be completely transparent. If you keep the path the same by using symbolic links, most things will work fine but eventually you'll probably run into problems with things that don't. If you change the path, then everyone who has stuff checked out will either have to abandon it and do fresh checkouts or else they will have to edit their CVS/Root files to point to the new location. -Larry Jones It COULD'VE happened by accident! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: moving a file
Massimiliano Cialdi writes: How can I rename a module without loose the files history? [...] how can I move a file from a directory to another whithout loose the history? http://www.cvshome.org/docs/manual/cvs_7.html#SEC70 -Larry Jones ...That would be pretty cool, if they weren't out to kill me. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS commit failure and lock files (under windows with cygwin)
Seth Copen Goldstein writes: cvs [commit aborted]: error writing to lock file $repository/,$file, where $repository is the path to the repository and $file is the file I am trying to commit. I have permissions in $repository and can touch ,file, there. But cvs fails. ANy suggestions? If you're using a network filesystem (e.g., a Windows share, AFS, NFS, Samba, etc.) to access the repository, that is almost certainly the source of the problem. Use client/server CVS with the repository locally mounted on the server instead. If not, you either have a hardware problem or you've found a bug in Cygwin. -Larry Jones Mom would be a lot more fun if she was a little more gullible. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: pserver problem
James P. Schmidt writes: cvs -d :pserver:(user@host):/usr/local/cvsrepos login (Logging in to (user@host)) CVS password: correct password cvs [login aborted]: unrecognized auth response from (host): Unknown command: `pserver' That means that your newly created server doesn't support pserver mode for some reason. On the server machine, run CVS with a bogus command: /usr/um/bin/cvs xxx That will give you a list of the valid commands -- you'll note that pserver isn't in the list. If server isn't on the list either, the problem is that configure couldn't find your TCP/IP socket library. If it is, then the problem is that configure couldn't find the crypt() function that's used for encrypting passwords for pserver. Check your configure output and post it here if you can't figure out how to fix it. You may also want to check with some knowledgeable Solaris people to see if crypt() is in a special library or if you have to install some special package to get it. Hmm, I just noticed that tcpwrappers appear to be in use on this machine. Changing /etc/inetd.conf to cvspserver stream tcp nowait root/usr/sbin/tcpd /usr/um/bin/cvs cvs --allow-root=/usr/local/cvsrepos pserver That's incorrect -- you need to get rid of the cvs when using tcpwrappers: cvspserver stream tcp nowait root /usr/sbin/tcpd /usr/um/bin/cvs --allow-root=/usr/local/cvsrepos pserver and... I get a different error: cvs [login aborted]: recv() from server (host): EOF That implies that tcpwrappers denied your connection. Check your hosts.allow and hosts.deny files for the appropriate rules. I strongly suggest getting it working without tcpwrappers first so you minimize the number of things that can go wrong. -Larry Jones Life's a lot more fun when you're not responsible for your actions. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS commit failure and lock files (under windows with cygwin)
On Thu, 12 Sep 2002, Larry Jones wrote: Seth Copen Goldstein writes: cvs [commit aborted]: error writing to lock file $repository/,$file, where $repository is the path to the repository and $file is the file I am trying to commit. I have permissions in $repository and can touch ,file, there. But cvs fails. ANy suggestions? If you're using a network filesystem (e.g., a Windows share, AFS, NFS, Samba, etc.) to access the repository, that is almost certainly the source of the problem. Use client/server CVS with the repository locally mounted on the server instead. If not, you either have a hardware problem or you've found a bug in Cygwin. If I may draw this point out slightly (I've had the same problem), can you tell us what CVS would be doing at the time? In what way does it try to create this lock file? Is there anything special or different about that? Any clue as to what would make this fail? I believe (from private corresopndence) that Seth is using AFS, as am I. This is the only case I've found in which AFS fails to correctly create a file. What I'm looking for is any suggestions or guesses as to what may be different in CVS' case... Mom would be a lot more fun if she was a little more gullible. -- Calvin Thanks for the Calvin quotations! At least half the reason I stay on this mailing list! :) Thanks, -David ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS commit failure and lock files (under windows with cygwin)
David Marshburn writes: If I may draw this point out slightly (I've had the same problem), can you tell us what CVS would be doing at the time? In what way does it try to create this lock file? Is there anything special or different about that? Any clue as to what would make this fail? I believe (from private corresopndence) that Seth is using AFS, as am I. This is the only case I've found in which AFS fails to correctly create a file. What I'm looking for is any suggestions or guesses as to what may be different in CVS' case... Lock file is a bit of a misnomer in this case -- it's actually the new RCS file. RCS uses the existence of the new file to prevent multiple updates at the same time and thus accurately calls it a lock file. CVS uses the same terminology even though it uses a completely different locking scheme. It does, however, create the file the same way that RCS does so that it will act as a lock against updating the file with RCS and CVS at the same time. (Because of the different locking schemes, however, it is extremely dangerous to use RCS on a CVS file. Since RCS doesn't honor CVS's locks, it's possible for CVS to wipe out RCS's changes.) What makes this error interesting is that *creating* the file is apparently successful; it's writing to it afterwards that fails somewhere along the way. If would be interesting to know from one of you that has the problem whether the file is actually created and, if so, what size it is. The relevant code is rcs_internal_lockfile() and rcs_internal_unlockfile() in src/rcs.c My guess is that the problem is that the file is opened for write, but the permissions are set to read only -- that should allow the opened file to be written to but not allow any subsequent opens to write to it, but perhaps that doesn't work right in AFS. Alternatively, the permissions of the open file are set immediately after opening it (provided your system has the fchmod() function); perhaps that has some unusual affect in AFS. -Larry Jones I stand FIRM in my belief of what's right! I REFUSE to compromise my principles! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: CVS commit failure and lock files (under windows with cygwin)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The file does not seem to exist after the failure, so either - - it was created, the error occurred, and then it was deleted, or - - it was not able to be created. Not sure how to tell which it is. - -seth BTW: Is there a short doc on how to use client/server securely from windows (client) to unix (server) and also to use pcl-cvs for all the above? - --- [EMAIL PROTECTED]7122 Wean Hall www.cs.cmu.edu/~seth School of Computer Science phone: 412-268-3828Carnegie Mellon University fax: 412-268-4801Pittsburgh, PA 15213 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 12:04 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: CVS commit failure and lock files (under windows with cygwin) David Marshburn writes: If I may draw this point out slightly (I've had the same problem), can you tell us what CVS would be doing at the time? In what way does it try to create this lock file? Is there anything special or different about that? Any clue as to what would make this fail? I believe (from private corresopndence) that Seth is using AFS, as am I. This is the only case I've found in which AFS fails to correctly create a file. What I'm looking for is any suggestions or guesses as to what may be different in CVS' case... Lock file is a bit of a misnomer in this case -- it's actually the new RCS file. RCS uses the existence of the new file to prevent multiple updates at the same time and thus accurately calls it a lock file. CVS uses the same terminology even though it uses a completely different locking scheme. It does, however, create the file the same way that RCS does so that it will act as a lock against updating the file with RCS and CVS at the same time. (Because of the different locking schemes, however, it is extremely dangerous to use RCS on a CVS file. Since RCS doesn't honor CVS's locks, it's possible for CVS to wipe out RCS's changes.) What makes this error interesting is that *creating* the file is apparently successful; it's writing to it afterwards that fails somewhere along the way. If would be interesting to know from one of you that has the problem whether the file is actually created and, if so, what size it is. The relevant code is rcs_internal_lockfile() and rcs_internal_unlockfile() in src/rcs.c My guess is that the problem is that the file is opened for write, but the permissions are set to read only -- that should allow the opened file to be written to but not allow any subsequent opens to write to it, but perhaps that doesn't work right in AFS. Alternatively, the permissions of the open file are set immediately after opening it (provided your system has the fchmod() function); perhaps that has some unusual affect in AFS. -Larry Jones I stand FIRM in my belief of what's right! I REFUSE to compromise my principles! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs -BEGIN PGP SIGNATURE- Version: 6.5.8ckt http://www.ipgpp.com/ iQA/AwUBPYDHOdqJMFyynoRZEQIAzACaA7ooTdu0Awek61rNirBK7fGmXqUAoPCk D8wWsTJ0/iRAMORn59srVnOU =/w03 -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: moving a file
[ On Thursday, September 12, 2002 at 16:26:28 (+0200), Massimiliano Cialdi wrote: ] Subject: moving a file how can I move a file from a directory to another whithout loose the history? $ cd .. $ cp foodir/barfile blahdir $ cvs rm -f foodir/barfile $ cd blahdir $ cvs add barfile $ cd .. $ cvs commit -m '- moved foodir/barfile to blahdir/barfile' foodir/barfile blahdir/barfile No history is lost. You should still be able to do cvs log foodir/barfile The final death entry in the log for the old file will tell you where the new file is and the first entry in the log of the new file will tell you where it came from. -- Greg A. Woods +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: no space on device - import
Larry Jones wrote: If you can move it without changing its full path and without using symbolic links, the move will be completely transparent. If you keep the path the same by using symbolic links, most things will work fine but eventually you'll probably run into problems with things that don't. If you change the path, then everyone who has stuff checked out will either have to abandon it and do fresh checkouts or else they will have to edit their CVS/Root files to point to the new location. Hmmm - although it would be rarely used, I think a CVS command: cvs relocate /old_root/ /new_root/ would be darn useful when needed... /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: moving a file
--- Forwarded mail from [EMAIL PROTECTED] [ On Thursday, September 12, 2002 at 16:26:28 (+0200), Massimiliano Cialdi wrote: ] Subject: moving a file how can I move a file from a directory to another whithout loose the history? $ cd .. $ cp foodir/barfile blahdir $ cvs rm -f foodir/barfile $ cd blahdir $ cvs add barfile $ cd .. $ cvs commit -m '- moved foodir/barfile to blahdir/barfile' foodir/barfile blahdir/barfile No history is lost. You should still be able to do cvs log foodir/barfile The final death entry in the log for the old file will tell you where the new file is and the first entry in the log of the new file will tell you where it came from. Using this method, technically, no history is lost. However, it is fragmented. You cannot use a single cvs log command to see the entire history of the file (before and after the move), and you can't use cvs update in the usual way to merge between branches if one of the contributors occurs in the post-move history. If you want the move to take effect on branches also, then you must create the branch tags on the post-move file and repeat the above process for each branch. If the post-move fills a location that was vacated by a prior removal, then there's an additional burden to sort out the fragments belonging to each incarnation of that path. And the bookkeeping complicates as the number of moves increases. In the end, you'll find it desirable to minimize the number reorganizations in your source tree. --- End of forwarded message from [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: no space on device - import
On Thu, Sep 12, 2002 at 10:50:49AM -0700, Mike Ayers wrote: cvs relocate /old_root/ /new_root This doesn't belong in CVS proper. It wouldn't hurt to have a supported (as opposed to ./contrib) script for it, if someone felt like writing one, and someone else felt like committing it :-) But failing even that, it's pretty simple; something along the lines of: newroot=... for f in `find $sandbox -type f -print | grep '/CVS/Root$'`; do echo $newroot $f done I used find | grep because find on its own can't filter for .../CVS/Root (GNU find can do it, but others can only do .../Root, which isn't specific enough.) -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / [...] despite reports to the contrary, it is the rare programmer who permanently loses his sanity while coding (permanently being the operative word). - Eric E. Allen ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
CVS and policy control
I am trying to find out how to handle policy control within CVS at the server level, just like the pre-op and post-op triggers within ClearCase. I have read about the files: loginfo taginfo rcsinfo editinfo commitinfo Can I modify taginfo to prevent deletion of branch tags and moving of tags (labels) that I created for baseline labels? Can I modify commitinfo to prevent checkin to the main trunk (we use main for the Production branch and all the developers work on side branches)? Can I modify commitinfo to prevent deletion of files from the repository? Also, do I modify CVS so that nobody else but myself can modify those *info files. and if so, how? Lastly, is there a way to modify ownership and permission of the files in the CVS repository so that they are owned only by the CVS administrator (similar to a post-op checkin trigger in ClearCase)? Thanks. Susan ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: moving a file
[ On Thursday, September 12, 2002 at 10:41:29 (-0700), Paul Sander wrote: ] Subject: Re: moving a file Using this method, technically, no history is lost. However, it is fragmented. You cannot use a single cvs log command to see the entire history of the file (before and after the move), and you can't use cvs update in the usual way to merge between branches if one of the contributors occurs in the post-move history. Such lame excuses you give. All of the above can still be done, and very easily too -- just not with one command. -- Greg A. Woods +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: moving a file
On Thu, 12 Sep 2002, Greg A. Woods wrote: [ On Thursday, September 12, 2002 at 10:41:29 (-0700), Paul Sander wrote: ] Subject: Re: moving a file Using this method, technically, no history is lost. However, it is fragmented. You cannot use a single cvs log command to see the entire history of the file (before and after the move), and you can't use cvs update in the usual way to merge between branches if one of the contributors occurs in the post-move history. Such lame excuses you give. All of the above can still be done, and very easily too -- just not with one command. It can if that command is spelled ``mcvs mv''. :P ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: moving a file
--- Forwarded mail from [EMAIL PROTECTED] [ On Thursday, September 12, 2002 at 10:41:29 (-0700), Paul Sander wrote: ] Subject: Re: moving a file Using this method, technically, no history is lost. However, it is fragmented. You cannot use a single cvs log command to see the entire history of the file (before and after the move), and you can't use cvs update in the usual way to merge between branches if one of the contributors occurs in the post-move history. All of the above can still be done, and very easily too -- just not with one command. All of the above, plus the stuff you omitted from your quote, can certainly be done and they do indeed require more than one command to accomplish. But by virtue of requiring multiple commands and a CVS admin's knowledge of how everything works plus extensive knowledge of the history of the project, it is a major annoyance to track this stuff. There's a lot to be said for a tool set that does not hinder progress, but in this context CVS is severely in the developers' faces. Under these conditions the CVS admin invariably receives many complaints about CVS being in the way. And in my opinion, they're reasonable in wanting a tool that does what they want with a single command. There's a strong desire to automate the sequence of commands to perform renames, logs, merges, and whatever else. But because there are so many special cases, and because the whole thing depends on the end users' comments, it simply can't be done with reliability. So while I don't disagree that this method can be used for source code reorganizations, I strongly disagree with your claim that using it is easy, particularly when it is used a lot within long-lived projects. --- End of forwarded message from [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Setting Up CVS to email notifications
I'm reading through Version Management with CVS (Per Cederqvist), and I'm a bit confused how I set up mail notifcations for my end users. I would like CVS to contact a mail server and send mail from a CVS_Admin account to the User_In_Question account when a file is being watched. From my reading I understand that I need to create a file in CVSROOT called users and that I have to put in a line like: user_in_question:[EMAIL PROTECTED] and then uncomment the relevant line in CVSROOT/notify. Are my assumptions correct? How do I configure the server to mail from a particular account? How do I configure the message body of the email? Exactly how is this working? Thanks a ton! ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS and policy control
I am trying to find out how to handle policy control within CVS at the server level, just like the pre-op and post-op triggers within ClearCase. I have read about the files: loginfo taginfo rcsinfo editinfo commitinfo Can I modify taginfo to prevent deletion of branch tags and moving of tags (labels) that I created for baseline labels? The question is whether a taginfo script can figure out that the tag it's being asked to move or delete is one you want to stop. If you use standard naming conventions for branches and baseline tags, you can check on the tag name. If not, I don't know any way to tell if the tag is a branch tag (and it might not be a branch tag on all files, although that's usually an error), and it could not tell a baseline tag from any other sort of revision tag. Possibly you could maintain a list (on the server, of course) of tags not to be messed with. Can I modify commitinfo to prevent checkin to the main trunk (we use main for the Production branch and all the developers work on side branches)? It doesn't say in the copy of the Cederqvist, I'm reading, or in Fogel's book, and I haven't experimented, but some people on the list have said that the commitinfo script runs in a directory with the files to be committed and the CVS directory of metadata. In that case, you can parse the CVS/Entries file to see if files are checked out on a tag. If the tag isn't a branch tag, CVS will stop the commit, so all you need do is check for a tag of any sort. Can I modify commitinfo to prevent deletion of files from the repository? Again, I haven't experimented, and the manuals are rather vague about this, but I would think you could identify a deleted file either by its not being present, or its being zero-length, or from CVS/Entries. Also, do I modify CVS so that nobody else but myself can modify those *info files. and if so, how? To do this, you want to be the only person with write permission in the CVSROOT repository directory. You should keep the scripts referred to by the *info files there, to keep them versioned and to keep them in the same security box as the *info files, and put their names in the checkoutlist file so CVS knows to check them out in the repository when you change them. If you want people to be able to check out these files and look at them, you need to give them read permission to the CVSROOT directory and write permission in a separate lock hierarchy (see http://www.thornleyware.com/scm/cvsconfig/cvsaccesscontrol.html for detailed and (I hope) helpful instructions). Lastly, is there a way to modify ownership and permission of the files in the CVS repository so that they are owned only by the CVS administrator (similar to a post-op checkin trigger in ClearCase)? I assume you're using CVS on a Unix box, rather than CVSNT on a Windows machine, because if the latter I don't really know. You don't modify file permissions (although it is necessary for anybody who's going to use the repository to have read access to them) but rather directory permissions, since CVS commits files by creating a new file and replacing the old. This of course does not restrict anybody who's checked the files out from doing what he or she wants in his or her sandbox. I don't know what you mean by a post-op checkin trigger, or why you would want file ownership. Can you clarify? -- Now building a CVS reference site at http://www.thornleyware.com [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
checkout without modifying the Entries file
Hi All, I've developed a release script which is version controlled, and which checks out and compiles a particular version of the product: ie cvs co proj cd proj release PROJ_V_1_1_1 which does: cvs co -rPROJ_V_1_1_1 -d%TEMP%\proj_temp cd %TEMP%\proj_temp build the problem is that since the checkout happened inside the project folder, the temp directory gets added to the entries folder and cvs tries to update the temp folder whenever the project folder gets updated. i'd rather not use cvs export because i like the idea of the release script updating version numbers based on the sticky tag. is there a way to get around this apart from temporarily renaming the CVS folder to pretend we're not in a checked out folder? Regards, Matthew Herrmann -- Far Edge Technology Level 11, 80 Mount St North Sydney NSW 2060 Australia Ph: 02 9955 3640 Mob: 0404 852 537 ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
