(newbieish) import is acting funny (at least to me)
Howdy, I've written a PHP script to attempt to create a module. Basically, it creates a dir, cd's into it, calls import, then removes the dir. The actual command looks like this: cvs -d /usr/home/chris/cvsroot import -m '' modulename arg1 arg2 This is the actual command string that's executed - I have PHP dump it to the screen right before it executes it. I also dump the response, which is No conflicts created by this import That should be good news, except that the module isn't created! I can't check it out, and there's nothing in $CVSROOT - it's simply not there. When I cut-n-paste the command to the console and enter it, the module does in fact get created. The only thing I can think of is that on the console I'm logged in as chris, but my Web server is a different user of course, so it's a user issue. However, I have other simple scripts to create a project, that basically work the same way, and they've succeeded. Any ideas? Thanks a lot, Chris
Re: can not lock a branch.
CVS has no facilities for changing this as far as I know. It's probably better just to use UTC in your other systems as well :) On Mon, Mar 05, 2001 at 06:47:17PM -0800, Li, James wrote: > > BTW, How to change cvs default time zone from UTC/GMT to my local PST. > > Thanks > > -James > > > -Original Message- > > From: Li, James > > Sent: Monday, March 05, 2001 3:34 PM > > To: '[EMAIL PROTECTED]' > > Cc: '[EMAIL PROTECTED]'; Li, James > > Subject:can not lock a branch. > > > > Hi, > > > > It will appreciate very much if you can help me this. I can not lock a > > branch from using cvs admin -l, Here is commands and error messages : I do > > not understant why cvs server cannot modify RCS file even I change the > > permition from 755 to 777 in /export/cvs/build? > > > > > cat /etc/group > > ... > > cvsadmin::501:cvs,twells,mboyd,alin,jli,build,test > > ... > > > whoami > > build > > > pwd > > /home/build/work > > >cvs co -r TEST_BRANCH build > > >cvs adm -lTEST_BRANCH build > > ... > > cvs server: cannot modify RCS file for `Errorcheck.sh' > > RCS file: /export/cvs/build/branch.build,v > > cvs server: /export/cvs/build/branch.build,v: branch TEST_BRANCH absent > > cvs server: cannot modify RCS file for `branch.build' > > RCS file: /export/cvs/build/build.log,v > > cvs server: /export/cvs/build/build.log,v: branch TEST_BRANCH absent > > cvs server: cannot modify RCS file for `build.log' > > RCS file: /export/cvs/build/build.sh,v > > cvs server: /export/cvs/build/build.sh,v: branch TEST_BRANCH absent > > cvs server: cannot modify RCS file for `build.sh' > > RCS file: /export/cvs/build/buildbytag.sh,v > > cvs server: /export/cvs/build/buildbytag.sh,v: branch TEST_BRANCH absent > > cvs server: cannot modify RCS file for `buildbytag.sh' > > ... > > > ls -l /export/cvs/ > > total 16 > > drwxrwxr-x 5 cvs cvsusers1536 Mar 5 15:24 build > > drwxrwxr-x 3 cvs cvsusers1536 Mar 5 15:15 CVSROOT > > drwxrwxr-x 3 cvs cvsusers 512 Nov 3 10:52 docs > > drwxrwxr-x 16 cvs cvsusers 512 Mar 5 15:21 prismedia > > > ls -l /export/cvs/build/ > > total 602 > > drwxrwxr-x 2 alin users512 Nov 27 14:18 Attic > > -r-xr-xr-x 1 alin users 1930 Feb 16 11:15 branch.build,v > > -rwxrwxrwx 1 buildusers 159932 Feb 14 18:23 build.log,v > > -rwxrwxrwx 1 buildusers 4040 Feb 14 18:23 build.sh,v > > -rwxrwxrwx 1 buildusers 1268 Feb 28 14:13 buildbytag.sh,v > > -rwxrwxrwx 1 buildusers937 Feb 14 18:23 buildtag,v > > -rwxrwxrwx 1 buildusers635 Feb 28 15:04 changemod.sh,v > > -rwxrwxrwx 1 buildusers 1023 Feb 14 18:23 cobytag.sh,v > > -rwxrwxrwx 1 buildusers 9087 Feb 28 14:32 current.build,v > > drwxrwxrwx 2 buildusers512 Jan 3 16:32 CVS > > -rwxrwxrwx 1 buildusers346 Feb 20 10:11 cvsaccess.conf, ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
(newbie) CVS training materials
Hi, I am new to CVS and finally got everything set up. I am looking for some training material to teach the group the basics of CVS. I don't want to intimate them with the big books. Is there a simplified version of the book that deals with checkout/update/commit/branching? I'd love to get a PowerPoint presentation for this purpose. OK, I am just lazy, but if someone is willing to share the materials, I am not going to complain. Thanks. Jiou-Pahn ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Looking for *real* docs
On Mon, Mar 05, 2001 at 09:27 -0600, David H. Thornley wrote: > > [ ... parsing command output with scripting languages ... ] > > As far as I know, there is no defined way to read this > information. This way suffers from the possibility that a > future revision will change the output (AFAIK, there are no > guarantees anywhere that this will not happen), but I'm the guy > who recommends when to install new versions, and evaluates > them, so I figure I can always change the scripts to accomodate > any changes. Isn't this one of the reasons the client/server protocol was designed for? It's versioned, negotiates capabilities (on both sides IIUC) and is well documented. Plus there are plenty of tools for network access from within your scripts. And hasn't there been some effort to build libs? Doesn't use cvs such a lib itself? To cut it short: I wouldn't go the route of parsing command output. Exactly for the reasons you state above. I'd rather look for a protocol that's made for machines instead of users. :) virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" [EMAIL PROTECTED] -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: can not lock a branch.
Title: RE: can not lock a branch. BTW, How to change cvs default time zone from UTC/GMT to my local PST. Thanks -James -Original Message- From: Li, James Sent: Monday, March 05, 2001 3:34 PM To: '[EMAIL PROTECTED]' Cc: '[EMAIL PROTECTED]'; Li, James Subject: can not lock a branch. Hi, It will appreciate very much if you can help me this. I can not lock a branch from using cvs admin -l, Here is commands and error messages : I do not understant why cvs server cannot modify RCS file even I change the permition from 755 to 777 in /export/cvs/build? > cat /etc/group ... cvsadmin::501:cvs,twells,mboyd,alin,jli,build,test ... > whoami build > pwd /home/build/work >cvs co -r TEST_BRANCH build >cvs adm -lTEST_BRANCH build ... cvs server: cannot modify RCS file for `Errorcheck.sh' RCS file: /export/cvs/build/branch.build,v cvs server: /export/cvs/build/branch.build,v: branch TEST_BRANCH absent cvs server: cannot modify RCS file for `branch.build' RCS file: /export/cvs/build/build.log,v cvs server: /export/cvs/build/build.log,v: branch TEST_BRANCH absent cvs server: cannot modify RCS file for `build.log' RCS file: /export/cvs/build/build.sh,v cvs server: /export/cvs/build/build.sh,v: branch TEST_BRANCH absent cvs server: cannot modify RCS file for `build.sh' RCS file: /export/cvs/build/buildbytag.sh,v cvs server: /export/cvs/build/buildbytag.sh,v: branch TEST_BRANCH absent cvs server: cannot modify RCS file for `buildbytag.sh' ... > ls -l /export/cvs/ total 16 drwxrwxr-x 5 cvs cvsusers 1536 Mar 5 15:24 build drwxrwxr-x 3 cvs cvsusers 1536 Mar 5 15:15 CVSROOT drwxrwxr-x 3 cvs cvsusers 512 Nov 3 10:52 docs drwxrwxr-x 16 cvs cvsusers 512 Mar 5 15:21 prismedia > ls -l /export/cvs/build/ total 602 drwxrwxr-x 2 alin users 512 Nov 27 14:18 Attic -r-xr-xr-x 1 alin users 1930 Feb 16 11:15 branch.build,v -rwxrwxrwx 1 build users 159932 Feb 14 18:23 build.log,v -rwxrwxrwx 1 build users 4040 Feb 14 18:23 build.sh,v -rwxrwxrwx 1 build users 1268 Feb 28 14:13 buildbytag.sh,v -rwxrwxrwx 1 build users 937 Feb 14 18:23 buildtag,v -rwxrwxrwx 1 build users 635 Feb 28 15:04 changemod.sh,v -rwxrwxrwx 1 build users 1023 Feb 14 18:23 cobytag.sh,v -rwxrwxrwx 1 build users 9087 Feb 28 14:32 current.build,v drwxrwxrwx 2 build users 512 Jan 3 16:32 CVS -rwxrwxrwx 1 build users 346 Feb 20 10:11 cvsaccess.conf,
can not lock a branch.
Title: can not lock a branch. Hi, It will appreciate very much if you can help me this. I can not lock a branch from using cvs admin -l, Here is commands and error messages : I do not understant why cvs server cannot modify RCS file even I change the permition from 755 to 777 in /export/cvs/build? > cat /etc/group ... cvsadmin::501:cvs,twells,mboyd,alin,jli,build,test ... > whoami build > pwd /home/build/work >cvs co -r TEST_BRANCH build >cvs adm -lTEST_BRANCH build ... cvs server: cannot modify RCS file for `Errorcheck.sh' RCS file: /export/cvs/build/branch.build,v cvs server: /export/cvs/build/branch.build,v: branch TEST_BRANCH absent cvs server: cannot modify RCS file for `branch.build' RCS file: /export/cvs/build/build.log,v cvs server: /export/cvs/build/build.log,v: branch TEST_BRANCH absent cvs server: cannot modify RCS file for `build.log' RCS file: /export/cvs/build/build.sh,v cvs server: /export/cvs/build/build.sh,v: branch TEST_BRANCH absent cvs server: cannot modify RCS file for `build.sh' RCS file: /export/cvs/build/buildbytag.sh,v cvs server: /export/cvs/build/buildbytag.sh,v: branch TEST_BRANCH absent cvs server: cannot modify RCS file for `buildbytag.sh' ... > ls -l /export/cvs/ total 16 drwxrwxr-x 5 cvs cvsusers 1536 Mar 5 15:24 build drwxrwxr-x 3 cvs cvsusers 1536 Mar 5 15:15 CVSROOT drwxrwxr-x 3 cvs cvsusers 512 Nov 3 10:52 docs drwxrwxr-x 16 cvs cvsusers 512 Mar 5 15:21 prismedia > ls -l /export/cvs/build/ total 602 drwxrwxr-x 2 alin users 512 Nov 27 14:18 Attic -r-xr-xr-x 1 alin users 1930 Feb 16 11:15 branch.build,v -rwxrwxrwx 1 build users 159932 Feb 14 18:23 build.log,v -rwxrwxrwx 1 build users 4040 Feb 14 18:23 build.sh,v -rwxrwxrwx 1 build users 1268 Feb 28 14:13 buildbytag.sh,v -rwxrwxrwx 1 build users 937 Feb 14 18:23 buildtag,v -rwxrwxrwx 1 build users 635 Feb 28 15:04 changemod.sh,v -rwxrwxrwx 1 build users 1023 Feb 14 18:23 cobytag.sh,v -rwxrwxrwx 1 build users 9087 Feb 28 14:32 current.build,v drwxrwxrwx 2 build users 512 Jan 3 16:32 CVS -rwxrwxrwx 1 build users 346 Feb 20 10:11 cvsaccess.conf,
Re: querying non-rtags?
Hi all, I noticed that the technical part of my question was answered by Larry Jones answering another question earlier on Sunday. So thanks, indirectly, for that. However, the "process advice" part of my question still stands. If any of you have the time, I'd definitely appreciate advice on that. Thanks, Alex Alexander Kamilewicz wrote: > > Hi all, > > I feel bad that since my original question a few months ago I haven't > tried to answer anyone else's questions. I hope that eventually I'll > feel comfortable enough with CVS to really help out people. > > That said, I need help. I know that: > > $cvs history -T -a | grep modulename > > will get me a listing of all rtags attached to modulename. Which is > good. However, I've recently developed a need to know what regular tags > (i.e. the result of cvs tag) have been applied to a certain module, > especially in the period since my last build (a build being when I apply > a rtag to the whole module's HEAD). > > Aside from going through every file via: > > $cvs log filename > > there doesn't seem like a way to do this. > > Why do you want to do this?, you might be asking. I don't blame you. > > Here's the scoop. The Powers That Be (TM) have decided that we want to > employ a "gatekeeper" structure for development & builds. The way this > works is as follows: > > 1. Developers do stuff and when they've finished a "feature" or, > perhaps "fix", they use $cvs tag tagname filenames to "tag" their work. > 2. After the code freeze and before the build (which is me doing cvs > rtag and then updating our test box with said tag), the "gatekeeper" > will look at all "tags" and decide what "features" and/or "fixes" will > go into the build. > 3. I'll do the build via a function of re-tagging the "features" or > "fixes" as that build version: > > $cvs rtag -r patchtag buildtag (this is both simpler than rtagging > every file that we want in the build, but also has the benefit of > excluding files that have been changed in the module but that we don't > want in the build) > > 4. If the build has problems, I can revert the changes by deleting the > rtag from the files in question ($cvs rtag -d buildtag filename), which > actually leads to a tangential question: > -is it possible to do this using patchtagname instead of filename? > -$cvs rtag -d buildtag patchtag, for instance, which didn't work for me > > If you've managed to fight off boredom and follow the above steps, > you'll see why it would be helpful for me to find a easy, quick & > painless way to find the developers' "tags" for their fixes and > features. > > Now, I _have_ figured out a way to do this, but it's cumbersome. Here > it is: > > 1. $cvs -q rdiff -s -r buildtag -r HEAD foomodule > diff > > This builds a file that lists all the files that changed with each line > looking something like: File foomodule/bar/zap.htm changed from 1.1 to > 1.2 > > 2. use "cut" to get rid of the stuff before and after the filenames > 3. use a script with the following bit to put "cvs log" in front of > each filename: > for i in 'cat diff' > do > echo cvs log $i > done > 4. run script > > OK, so that's it! Thus, I've got 2 questions: > > 1. Is there any easier way to accomplish that which I've laid out > above? > 2. Does anyone have similar experience to this kind of development > "environment" with these needs and how did you fulfill them? > > Thanks a ton in advance! ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Unusual error message
Hi, Someone in our organization used "cvs commit" to commit several files. However, so far as I can tell, the files were not updated. The history files indicate that the files were checked in, though. Now, whenever anyone trys to commit any file, error messages are printed for each and every one of the aforementioned files: cvs update: move away Makefile; it is in the way cvs update: move away . I cannot determine what this message means. However, the master source directory contains CVS/Entries which contains no mention of the aforementioned files. Thanks in advance for your time and consideration. Trent -- Trent Eggleston (925) 449-2500 x 245 Livermore Software Tech. Corp. [EMAIL PROTECTED] 7374 Las Positas Road Livermore, CA 94550
Re: merge/diff
Great idea, thanks Mike! For the record, here's what I did: cvs diff -bw -r HEAD -r branch-tag filename > patch.txt vi patch.txt patch < patch.txt I was a bit surprised when the patch applied cleanly after I had (carefully) hacked a bunch of stuff out, only one hunk failed and everything else worked out great. A few minor edits the resulting file and I'm away. Thanks again! Cheers, Derek Mike Castle wrote: > > On Fri, Mar 02, 2001 at 03:52:03PM -0700, Derek Scherger wrote: > > Is there any way to control the diffing done by cvs update -j so that it > > ignores whitespace differences? At the moment I'm reduced to manually > > applying the changes that cvs diff -bw sees rather than trying to fix up > > the conflicts caused by merging. Neither situation is particularly > > pleasant however! > > If you do a cvs diff -bw -u and then use patch, do you get fewer conflicts than > using cvs straight forward? > > I know that in the past I had a situation where I could not get cvs to > merge and had to resort to using the patch program externally after > generating diffs in a slightly different manner. > > mrc > -- >Mike Castle Life is like a clock: You can work constantly > [EMAIL PROTECTED] and be right all the time, or not work at all > www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc > We are all of us living in the shadow of Manhattan. -- Watchmen > > ___ > Info-cvs mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs checkout hangs with ssh2?
This is a bug in SSHv2. You must use SSHv1 as an RSH replacement for the time being. I have had no problems running CVS through an SSHv2 tunnel however, so if you want to bind pserver to the loopback and tunnel in that would work ok. On Mon, Mar 05, 2001 at 11:06:45AM -0600, John D. DeHart wrote: > > When I try to do a large checkout using cvs over ssh2, my server hangs. > WHen I do the same checkout over ssh1 I don't have this problem. > Has anyone else seen this? Any suggestions? > > Here are the particulars: > server: > OS: NetBSD 1.4.1 > > ssh2 version 2.0.12 > cvs version: 1.10 > > ssh1 version: 1.2.27 > cvs version: 1.10 > > client: > OS: NetBSD 1.4.1 > ssh2 version: 2.1.0 > ssh1 version: 1.2.27 > > On the client I am using: > > setenv CVSROOT :ext:hostname:/cvsroot_path > > setenv CVS_RSH ssh1 > OR > > setenv CVS_RSH ssh2 > > Thanks for any help. > > John > [EMAIL PROTECTED] > > > > ___ > Info-cvs mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/info-cvs > ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Standalone CVS pserver
On Thu, Mar 01, 2001 at 04:22:26PM -, Darren Young wrote: > I read a thread from last year that mentioned the same type of issue > I am looking to resolve, although I did not find any appropriate > answers. I am looking to set up a cvs pserver, however it will be > located on my hosting provider's machine. I have shell access and > have compiled/installed 1.11 with --prefix=$HOME. Now, what I would > like to do is something like this: > >$HOME/bin/cvs --allow-root=$HOME/cvsroot -T$HOME/tmp -f pserver & > > It seems to start fine, although if I touch my keyboard it stops. In > a second shell session, netstat -na | grep 2401 doesn't show me > listening() either.? > > Also, I'd like to change the default port from 2401 to something > else, from what I have seen I need to modify CVS_AUTH_PORT in > client.h and recompile, correct? It seems as though there is no way > to set this at run-time. > > Has anyone successfully done this, if so, what details am I missing? > By the way, the machine that I am running this on is a RedHat > 6.2/2.2.16-3. You might want to use inetd. You can run this as a normal user too. You do not need root privileges to run inetd with a cvs pserver. I am going to run a cvs pserver with about 40 repositories, which for some reasons need to be completely distinct, I ran into the problem that most inetd implementations limit the number of parameters. For that reason I hacked a standalone cvs pserver, which currently is a wrapper around normal cvs derived from a port of OpenBSD inetd to Linux by Thorsten Kukuk. If you want to test it, you can get it from http://webrum.uni-mannheim.de/math/rschiele/cvspserver/ It currently supports Linux (tested on glibc 2.1 and 2.2), but might as well work on other systems (with some changes). There is some short description in the source file. If it is not understandable, feel free to contact me. Further plans are to make a patch against normal cvs to make it support this functionality directly. Feedback is welcome. Robert -- Robert Schiele mailto:[EMAIL PROTECTED] Tel./Fax: +49-621-10059 http://webrum.uni-mannheim.de/math/rschiele/ PGP signature
RE: How to get "edit -c" working
Ahh, I see the problem. You need some way to tell everyone that the database stuff is being worked on. You're thinking of using CVS as the mechanism to do so. I think I would use the "cvs edit -c" patch for this situation. Noel [EMAIL PROTECTED] on 2001.03.02 13:54:59 (see below) > [EMAIL PROTECTED] on 2001.02.28 12:30:31 > >Some things can't be easily versioned under CVS. For example, PL/SQL or > >other code that lives in the database. Since it's a shared > resource, we need > >to do exclusive locking to version it. > > Is there a way to export/import these files as text? If so, you > can go that > route. That what we've done (exported the files as text), and then as part of the checkin process, the DB guys are supposed to commit the change and unlock the file. Could you tell me more about what you're thinking about here as an alternative? Wait, let me back up. Here's a better explanation of why I think this part needs locking. The DB developers have fancy tools to allow them to edit, run, and debug their code directly in the (single, shared) database. But no tools to keep versions of the code. They need to keep using those fancy tools. But when one person is fancily editing the code directly in the DB, we want to have a portion of the development process inform others that they're not allowed to edit that piece of code. I had been thinking, export all the DB code as text, and use exclusive locking. We're supposed to be using CVS everywhere, not an amalgam of tools, so I really want to get CVS locking working. But I'm open to another suggestion if I've missed something. I can't think of how concurrent development would work with a shared database. So it sounds like I need to dowload all the patches, apply them, build new UNIX and Windows executables with the patches, patch our WinCVS installation with the new binary, and update everyone's installation. Gaack :) Has anyone pre-built the windows cvs.exe with Noel's patches? > >So the recommend workaround is to use Noel Yap's "cvs edit -c" patch (hi > >Noel!) against CVS 1.10.8. > > > >I took a look on Sourceforge and there are just zillions of patches to > >download. Which ones are the ones I need? > > I apologize for the format of these patches. I should've > submitted one patch > per feature/bug fix, but instead, I submitted incremental > patches. Since they > are incremental, you'll have to install each patch up to and > including the last > one you need. > > >Also, and very importantly, is this a server-only patch, or will > I have to > >patch all the clients as well? > > The patch are both server and client side. New options have to > be since the > client will need to be able to specify the option, and the server > will need to > understand it. > > >thanks *so much*, > >Chris Chambers > > I apologize again for the messiness. I know I keep saying this, > but if I find > some time, I'll clean up the patches. > > Noel > > > > This communication is for informational purposes only. It is not > intended as > an offer or solicitation for the purchase or sale of any > financial instrument > or as an official confirmation of any transaction. All market prices, data > and other information are not warranted as to completeness or accuracy and > are subject to change without notice. Any comments or statements > made herein > do not necessarily reflect those of J.P. Morgan Chase & Co., its > subsidiaries and affiliates. > > > ___ > Info-cvs mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/info-cvs > ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
cvs checkout hangs with ssh2?
When I try to do a large checkout using cvs over ssh2, my server hangs. WHen I do the same checkout over ssh1 I don't have this problem. Has anyone else seen this? Any suggestions? Here are the particulars: server: OS: NetBSD 1.4.1 ssh2 version 2.0.12 cvs version: 1.10 ssh1 version: 1.2.27 cvs version: 1.10 client: OS: NetBSD 1.4.1 ssh2 version: 2.1.0 ssh1 version: 1.2.27 On the client I am using: > setenv CVSROOT :ext:hostname:/cvsroot_path > setenv CVS_RSH ssh1 OR > setenv CVS_RSH ssh2 Thanks for any help. John [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Defining modules
Michael Lukaschek writes: > > is there a way to define modules consisting of some other modules (other > modules are defined in modules file, but they are not the real modules > name, they are aliases... )? http://www.cvshome.org/docs/manual/cvs_18.html#SEC155 Both alias modules and ampersand modules can refer to other modules. > Is there a way to specify a branch in the modules file? I want to define > a module using a specified branch of another module... No. You're not the first person to express an interest in this -- if anyone is looking for a CVS enhancement project, this might be a good one. -Larry Jones Oh, what the heck. I'll do it. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: obtaining tags
Rob Helmer writes: > > What's the easiest way to grab a list of tags for all files > in a given repository? I'd like to do this for part of my > build system. There isn't one. Tags are stored in each file separately (there's no central record) so you'd have to read through every file in the repository, which could take quite a while. For a set of checked-out files, both ``cvs log'' and ``cvs status -v'' will give you a list of tags in each file, which may be of some help. -Larry Jones Kicking dust is the only part of this game we really like. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: (newbie) Where is the project message?
Chris writes: > > When I create a project using import, I specify a message with -m. But I > can't find out where to view that message. log doesn't seem to get it. Log only works in a working directory. If you check out your project and then do ``cvs log'' on one of the checked-out files, you'll see your message. -Larry Jones Oh, now don't YOU start on me. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Looking for *real* docs
Chris wrote: > > Howdy, > > I'm trying to write some code to allow you to browse a repository. Crucial > to this is thorough documentation of how to query the repository for name & > message information (through using 'log', I guess), as well as > documentation for the output of such commands, so I can parse it. I've read > man pages for rcs, rlog, and cvs, along with additional online material > including the Perdeqvist (sp) thingee, and I can't find anything, or even a > reference to what I'm looking for. > I looked at the output for "cvs stat -v" and picked out the lines of output that contained information I wanted, and made Perl regexps that would extract it. Nothing fancy. I didn't, and don't, know of a better way to do this. As far as I know, there is no defined way to read this information. This way suffers from the possibility that a future revision will change the output (AFAIK, there are no guarantees anywhere that this will not happen), but I'm the guy who recommends when to install new versions, and evaluates them, so I figure I can always change the scripts to accomodate any changes. > There are several add-on tools that do this, and I could plow through their > source if need be, but I'd rather not - I'd rather read what the > tool-makers read, whatever that is. > Reasonable question, but the answer is that you've found all the documentation I have. -- David H. Thornley Software Engineer at CES International, Inc.: [EMAIL PROTECTED] or (763)-694-2556 at home: (612)-623-0552 or [EMAIL PROTECTED] or http://www.visi.com/~thornley/david/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Defining modules
Hello, is there a way to define modules consisting of some other modules (other modules are defined in modules file, but they are not the real modules name, they are aliases... )? Is there a way to specify a branch in the modules file? I want to define a module using a specified branch of another module... Thanks for your help, Michael -- Dipl.-Math. Michael Lukaschek, Software Development Interzart AG 3D Commerce / Dimension 3D-Systems GmbH Phone: +49-511 390884-0 Fax: +49-511 390884-10 mailto:[EMAIL PROTECTED] http://www.dimension-3d.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
