Re: Newbie Q: cannot open CVS/Entries for reading
Albin Takami wrote: Yes, I have tried this and it's works. Would replacement of checkout with co result in the exact same thing? `cvs checkout` and `cvs co` are the same command, so yes. /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Q: cannot open CVS/Entries for reading
Larry Jones wrote: Mike Ayers writes: So if you are using CVS properly, the CVSROOT env var never comes into play. I think you're overstating the case. Most people just use a single repository and even people who use multiple repositories usually have one repository that they use more often than others. In those cases, it makes sense to set $CVSROOT so you don't have to explicitly set it on the command line even for checkout (or import!) in most cases. Whoops! That should have read may never or almost never, assuming that checking out clean trees or importing are rarely done. In either case, setting an environmental variable, the procedure intended for making permanent changes to one's computing environment, does not seem to be the proper way to do this. I am glad for the new way, and push it, because CVSROOT was never a good way to do this. /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Q: cannot open CVS/Entries for reading
Mike Ayers writes: Whoops! That should have read may never or almost never, assuming that checking out clean trees or importing are rarely done. In either case, setting an environmental variable, the procedure intended for making permanent changes to one's computing environment, does not seem to be the proper way to do this. I am glad for the new way, and push it, because CVSROOT was never a good way to do this. But you still seem to be treating it as an either/or proposition, and it's not. It makes a lot of sense to set $CVSROOT to your default repository and then override it with -d on the command line when necessary. -Larry Jones Hello, I'm wondering if you sell kegs of dynamite. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Q: cannot open CVS/Entries for reading
Mike Ayers writes: So if you are using CVS properly, the CVSROOT env var never comes into play. I think you're overstating the case. Most people just use a single repository and even people who use multiple repositories usually have one repository that they use more often than others. In those cases, it makes sense to set $CVSROOT so you don't have to explicitly set it on the command line even for checkout (or import!) in most cases. -Larry Jones From now on, I'm devoting myself to the cultivation of interpersonal relationships. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Newbie Q: cannot open CVS/Entries for reading
-Original Message- From: Mike Ayers [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 13, 2002 8:33 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject:Re: Newbie Q: cannot open CVS/Entries for reading Albin Takami wrote: -Original Message- From: Mike Ayers [mailto:[EMAIL PROTECTED]] Albin Takami wrote: `cvs checkout /design/project/dig/V9/src` is incorrect syntax. If you have built module src in CVSROOT /design/project/dig/V9, then you should: $ cvs -d /design/project/dig/V9 checkout src Have you tried this? Well, have you? Yes, I have tried this and it's works. Would replacement of checkout with co result in the exact same thing? /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Newbie Q: cannot open CVS/Entries for reading
-Original Message- From: Mike Ayers [mailto:[EMAIL PROTECTED]] Sent: Saturday, August 03, 2002 7:56 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject:Re: Newbie Q: cannot open CVS/Entries for reading Order scrambled to get thought flow... Albin Takami wrote: To clarify, the repository location is the directory that you set the CVSROOT variable to, right? Yes, but you should not need to set CVSROOT - in fact, I recommend you don't. Use the -d flag during checkout, and let the CVS directories track the repository for you. I've done some more reading and it seems like Karl Fogel and Cederquist's book suggests that I should set CVSROOT in .cshrc. So, I was wondering what the benefits and drawbacks are for not setting CVSROOT in .cshrc, according to you? Tried importing: cvs import -m Imported sources /design/project/dig/V9/src digital start The system replies: directory /design/project/dig/V9/src is not relative within the repository That command makes no sense. What are digital and start? This is from the Reservist manual too (sect 3.1.1): cvs import -m Imported sources yoyodyne/rdir yoyo start I replaced the so called vendor tag yoyo with digital since yoyo didn't help me. Well, I don't remember what I set in there, because I haven't use the vendor tag since import, so yoyo probably wouldn't have hurt you either. However, you are trying to import into an existing repository. While this is possible, and can be useful, it is not what you want to do. `cvs checkout /design/project/dig/V9/src` is incorrect syntax. If you have built module src in CVSROOT /design/project/dig/V9, then you should: $ cvs -d /design/project/dig/V9 checkout src Have you tried this? /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Q: cannot open CVS/Entries for reading
Albin Takami wrote: -Original Message- From: Mike Ayers [mailto:[EMAIL PROTECTED]] Albin Takami wrote: To clarify, the repository location is the directory that you set the CVSROOT variable to, right? Yes, but you should not need to set CVSROOT - in fact, I recommend you don't. Use the -d flag during checkout, and let the CVS directories track the repository for you. I've done some more reading and it seems like Karl Fogel and Cederquist's book suggests that I should set CVSROOT in .cshrc. So, I was wondering what the benefits and drawbacks are for not setting CVSROOT in .cshrc, according to you? Okay, this may not be a perfect explanation, as I have not had time to fact check all this, but... Originally, one pointed to one's archive via CVSROOT. However, this becomes a problem as soon as the second archive is accessed. Now one must change env var values every time one changes one's work tree - a problematic way to manage the issue. So our thoughtful CVS developers came up with an excellent solution: each directory of the sandbox swould have a directory in it named CVS that held files which helped CVS operate. One of those files, named Root, contains the location of the CVS root directory. It is automatically created and properly set when you checkout the development tree. The order in which CVS looks for a root is: 1) The -d flag on the command line of a cvs command 2) The Root file in the CVS subdirectory of the directory in which you are operating. 3) The CVSROOT env var. So if you are using CVS properly, the CVSROOT env var never comes into play. Note that in many respects, Cederqvist is out of date. This is one of them. `cvs checkout /design/project/dig/V9/src` is incorrect syntax. If you have built module src in CVSROOT /design/project/dig/V9, then you should: $ cvs -d /design/project/dig/V9 checkout src Have you tried this? Well, have you? /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Newbie Q: cannot open CVS/Entries for reading
Hi and thanks for the reply. 4. *.v files are written in a hardware description language called Verilog. Which is used to design integrated circuits like CPU, DSP, Application specific IC (ASIC) and MCU (Micro controller) for PCs, car, microwave, cell phones, sprinkler system etc. The syntax is similar to *.c (ANSI C) files for software. 5.5 Peggy never checked out any files/module because the files she is trying to check-in/commit are new files (first time check-in). Hope that clarifies things. Albin -Original Message- From: Mike Ayers [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 01, 2002 8:21 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject:Re: Newbie Q: cannot open CVS/Entries for reading H Albin Takami wrote: 4. Checked in/committed a bunch of files with cvs ci *.v What are *.v files? (Just curious) 5. I setup the .cshrc file for another user, Peggy. 5.5 When did Peggy do `cvs checkout project/module`? This is when the CVS directories get created. That's all I can think of /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Q: cannot open CVS/Entries for reading
Albin Takami wrote: 5.5 Peggy never checked out any files/module because the files she is trying to check-in/commit are new files (first time check-in). *BZZZT* Sorry... This is the problem. Once a project is created, in order to work in the project, one must first check out the project tree. (Strictly speaking, this is not true, but it requires a great deal of skill in CVS to work without the project tree). Then, when committing files, CVS has a context to work from, as saved in the CVS directories in the project tree. So if Peggy checks out the project, moves her files into the project tree, and commits them from there, ahe will have no problem. /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Q: cannot open CVS/Entries for reading
Albin Takami wrote: 5.5 Peggy never checked out any files/module because the files she is trying to check-in/commit are new files (first time check-in). Um, did Peggy `cvs add' the files before attempting to check them in? Derek -- *8^) Email: [EMAIL PROTECTED] Public key available from www.keyserver.net - Key ID 5ECF1609 Fingerprint 511D DCD9 04CE 48A9 CC07 A421 BFBF 5CC2 56A6 AB0E Get CVS support at http://ximbiot.com -- This punishment is not boring and pointless. This punishment is not boring and pointless. This punishment is not boring and pointless... - Bart Simpson on chalkboard, _The Simpsons_ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Newbie Q: cannot open CVS/Entries for reading
Mike, Thanks for your reply and suggestions Derek and Mike. ...Check out the project tree... Ok, according to the Cederquist (p31): cvs checkout /design/project/dig/V9/src The system replies: cannot find module '/design/project/dig/V9/src' - ignored FYI: The CVSROOT variable for Peggy and me is set to /design/project/dig/V9 and the only system related differences is that she is running c-shell and I run t-shell. Tried importing: cvs import -m Imported sources /design/project/dig/V9/src digital start The system replies: directory /design/project/dig/V9/src is not relative within the repository Since she had problem checking out her project tree, she copied her files from her directory to /design/project/dig/V9/src and tried to check them in, however it was the same result as I initially got (I don't have any problem checking her files in). Derek, I tried adding: /design/project/dig/V9/src/cvs add abc.v The system replies: [add aborted]: there is no version here; do 'cvs checkout' first Lastly, tried to checkout a file as Peggy or myself: cvs /design/project/dig/V9/src/cvs checkout abc.v System replies: cannot find module 'abc.v' - ignored The file abc.v is already in cvs /design/project/dig/V9/src/ directory and has been checked in once (it has a abc.v,v) file generated. What else can I do to find the problem? Albin -Original Message- From: Mike Ayers [mailto:[EMAIL PROTECTED]] Sent: Friday, August 02, 2002 12:41 PM To: [EMAIL PROTECTED] Cc: 'Mike Ayers'; [EMAIL PROTECTED] Subject:Re: Newbie Q: cannot open CVS/Entries for reading Albin Takami wrote: 5.5 Peggy never checked out any files/module because the files she is trying to check-in/commit are new files (first time check-in). *BZZZT* Sorry... This is the problem. Once a project is created, in order to work in the project, one must first check out the project tree. (Strictly speaking, this is not true, but it requires a great deal of skill in CVS to work without the project tree). Then, when committing files, CVS has a context to work from, as saved in the CVS directories in the project tree. So if Peggy checks out the project, moves her files into the project tree, and commits them from there, ahe will have no problem. /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Newbie Q: cannot open CVS/Entries for reading
-Original Message- From: Mike Ayers [mailto:[EMAIL PROTECTED]] Sent: Friday, August 02, 2002 4:23 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject:Re: Newbie Q: cannot open CVS/Entries for reading Albin Takami wrote: ...Check out the project tree... Ok, according to the Cederquist (p31): cvs checkout /design/project/dig/V9/src The system replies: cannot find module '/design/project/dig/V9/src' - ignored Cederqvist is generally distributed as an HTML file. Please quote sections, not pages. This is preferred practice for all technical documentation, as it spans revisions better. Ok, it was section 3.1.1. I used the PDF-format version. `cvs checkout /design/project/dig/V9/src` is incorrect syntax. If you have built module src in CVSROOT /design/project/dig/V9, then you should: $ cvs -d /design/project/dig/V9 checkout src Tried importing: cvs import -m Imported sources /design/project/dig/V9/src digital start The system replies: directory /design/project/dig/V9/src is not relative within the repository That command makes no sense. What are digital and start? This is from the Reservist manual too (sect 3.1.1): cvs import -m Imported sources yoyodyne/rdir yoyo start I replaced the so called vendor tag yoyo with digital since yoyo didn't help me. Since she had problem checking out her project tree, she copied her files from her directory to /design/project/dig/V9/src and tried to check them in, however it was the same result as I initially got (I don't have any problem checking her files in). Ummm - if she copied her files directly into the repository and started mucking around there, she may have damaged the repository. To clarify, the repository location is the directory that you set the CVSROOT variable to, right? I tried adding: /design/project/dig/V9/src/cvs add abc.v The system replies: [add aborted]: there is no version here; do 'cvs checkout' first The system agrees with me. Lastly, tried to checkout a file as Peggy or myself: cvs /design/project/dig/V9/src/cvs checkout abc.v System replies: cannot find module 'abc.v' - ignored This is correct behavior. Modules, not files, get checked out. The files are contained in the modules. Ok, modules in the Verilog language is also file independent, however they have different meaning than in cvs. Anyhow, I found out that the modules file is checked in, and the co command was used as an alias for changing directory to a project directory, so I could not check out the modules file. That is now fixed. What else can I do to find the problem? Spend a lot more time reading documentation. Cederqvist, BTW, is a great reference manual, but a terrible introduction. Try http://www.cvshome.org/docs/blandy.html or http://cvsbook.red-bean.com/cvsbook.html, which may be better for getting started. /|/|ike Thanks a lot! Albin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Q: cannot open CVS/Entries for reading
H Albin Takami wrote: 4. Checked in/committed a bunch of files with cvs ci *.v What are *.v files? (Just curious) 5. I setup the .cshrc file for another user, Peggy. 5.5 When did Peggy do `cvs checkout project/module`? This is when the CVS directories get created. That's all I can think of /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
