Compilation of cvs
'lo all. I am currently trying to get a static compilation of cvs on a freebsd 4.5 system. what I am trying to do is >./configure --disable-client >make configure goes well but get some errors on a make. snipit==logmsg.c: In function `do_editor':logmsg.c:198: structure has no member named `isremote'logmsg.c:199: structure has no member named `isremote'*** Error code 1Stop in /usr/home/temp/cvs-1.11.2/src.*** Error code 1Stop in /usr/home/temp/cvs-1.11.2/src.*** Error code 1Stop in /usr/home/temp/cvs-1.11.2.*** Error code 1Stop in /usr/home/temp/cvs-1.11.2.===Any ideas would be apreciated. I did get it to compile on RH 7.x but on freebsd I have triedcvs-1.11cvs-1.11.1p1cvs-1.11.2and all have thrown errors :(any help would be appreciated. thanks in advanceMatthew Frick.
Re: can't add with wincvs
Yep. That was it. I hadn't let it create the directory on my local machine. At least now that I know that it works, I think that I can tell the customer that it does work and if they want to use it, but don't know how, that THEY should now start reading. Thanks Steve At 02:16 AM 11/5/2002 -0800, you wrote: Steve Buehler wrote: Ok. I was able to get a private key setup and running so that it logs me in. Now I am running into another problem. I can connect to the server. In fact, in WinCVS, I can even do a create which gives me the following reply in WinCVS: cvs init *CVS exited normally with code 0* WHOA, Nelly! Where's the `cvs checkout` that you MUST do between these two paragraphs? Even with no files in the repository, it will set up your CVS directory. Now. When I go again and click on a file to add (testz.php), then click on the "Add Selected" button, I get this: cvs add testz.php (in directory C:\ijobs\cvs\) cvs add: in directory .: cvs [add aborted]: *PANIC* administration files missing Sounds like it couldn't find the CVS directory... -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ow3 ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Problem: About repositiory
--- "Riechers, Matthew W" <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > > > A. checkout new working dir using new repository > location > > B. transfer content of old working copy to new > working copy > > C. delete and cvs remove files from new working > copy if necessary > > D. get rid of old working copy and continue work > in new working copy > > That is pretty fool-proof, but you lose existing > intermediate build > files, which may or may not be a big deal. This is extremely dangerous! You will lose the version that was originally checked out thereby possibly overwriting changes that have already been checked in. Noel __ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Providing the functionality of CVS as a library
Ah, completely forget - someone that I contacted on this list before sent me the beginnings of a library written in Perl for the cvs client/server protocol. I just took a look at it again yesterday, it is written well, there is a library and a sample client, the library only implements a couple commands so far, it's enough to do checkout/status/etc. The client assumes that you are using pserver, I don't see any reason you couldn't have a pipe to "cvs server" running through SSH though. The client is simple, it doesn't maintain "CVS" metadata dirs or anything, prints everything ( checkouts, etc ) to STDOUT. It would be kind of neat to have a complete Perl CVS client just as a proof-of-concept on the library though, I'll take a serious look at it once I get some of my other projects a little further along :) I've been thinking of replacing SandWeb's Repository::cvs with a better version of this library, it poses some problems with regard to supporting UNIX accounts in the way I'd like to, but nothing unsurmountable. Let me know if you'd like a copy, it's Artistic license/LGPL ( like Perl ). I haven't made any changes to it yet, just looked at it. Thanks, Rob On Sun, Nov 03, 2002 at 10:31:15PM -0800, Rob Helmer wrote: > On Mon, Nov 04, 2002 at 12:08:01AM -0500, Alex Taler wrote: > > > "Rob" == Rob Helmer <[EMAIL PROTECTED]> writes: > > Rob> We looked at VCS::Cvs for inclusion into SandWeb, and realized the same > > Rob> thing, so we wrote our own abstracted Perl CVS class ( > > Rob> SandWeb::Repository::cvs ). > > > > Rob> If you want to check it out, I'd reccommend getting the CVS version - > > Rob> http://sandweb.sf.net > > > > Thanks, I took a look at it. It doesn't look quite like what I > > want. I am thinking of an API in which the managed CVS files are > > individual objects which you can manipulate. Along the same > > lines as in VCS::Cvs. The benefit I see to this approach is > > better handling of unusual cases. How do you handle error and > > unusual cases? ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Multiple environment mgt with CvS...
Hello all - I'm really new to the CvS world, so please bear with me on this question: We are using CvS on Unix with WinCvS user interface. We have around 12 developers and are working with multiple environments. Each of these environments will be used by a different testing group, so we may need to support different versions of the same code in all of these environments. Once we start deploying code to these environments and the users start reporting issues in them, we'll need a strategy for fixing bugs in the appropriate environment, and re-deploying the code there for re-testing. Chances are, however, that we will need to merge some of the fixes from these individual environments into the 'Base' code in the other environments so as to eliminate the same bugs accross multiple environments. This, however, seems like a very complicated task because we want to be selective about what to merge in order not to introduce features from the on-going development in other areas... So the broad question is this: What is the best practice for getting our hands around all these environments and for developing a solid processes so we don't step on each other's toes?! Thanks, James
Re: Newbie Problem: About repositiory
Hello Mathew, re intermediate build files, I don't quite see why you'd have to lose them. Just copy them over. To clarify, what I meant by step B is a raw copy of every file in your old working dir to the new working dir. AFAICT the only thing you have to worry about are files that you got rid of in the old working directory and which show up in the new working directory. Probably those files were deleted and 'cvs remove'd but not yet committed. So that information will be lost, but that's just a matter of 'cvs remove'ing them again. The basic idea of a new checkout and a raw copy is actually a renewal of the CVS/Root files without bypassing cvs. That said, I agree that the other solution sounds better. Haven't had the chance to test it though I guess you've taken care of that. Erik "Riechers, Matthew W" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 11/05/2002 03:25 PM To: [EMAIL PROTECTED] cc: Mike Ayers <[EMAIL PROTECTED]>, CVS <[EMAIL PROTECTED]>, i Xicheng Jia <[EMAIL PROTECTED]> Subject:Re: Newbie Problem: About repositiory [EMAIL PROTECTED] wrote: > > A. checkout new working dir using new repository location > B. transfer content of old working copy to new working copy > C. delete and cvs remove files from new working copy if necessary > D. get rid of old working copy and continue work in new working copy That is pretty fool-proof, but you lose existing intermediate build files, which may or may not be a big deal. > Mike Ayers <[EMAIL PROTECTED]> > > 4. Run a script which deletes all the CVS/Root > directories and then > `cvs -d /new/path/to/repository update` s/directories/files/ and this works. Nice tip! Much better than running N processes to delete/modify existing files... Also note that if $CVSROOT is defined to the new location, you can just 'cvs up'. -Matt ___ 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: Newbie Problem: About repositiory
[EMAIL PROTECTED] wrote: > > A. checkout new working dir using new repository location > B. transfer content of old working copy to new working copy > C. delete and cvs remove files from new working copy if necessary > D. get rid of old working copy and continue work in new working copy That is pretty fool-proof, but you lose existing intermediate build files, which may or may not be a big deal. > Mike Ayers <[EMAIL PROTECTED]> > > 4. Run a script which deletes all the CVS/Root > directories and then > `cvs -d /new/path/to/repository update` s/directories/files/ and this works. Nice tip! Much better than running N processes to delete/modify existing files... Also note that if $CVSROOT is defined to the new location, you can just 'cvs up'. -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: A silly problem: About co & ci
Xicheng Jia wrote: > > I am wondering if or not there is any difference between "co" and > "checkout", also between "ci" and "commit"? They are synonyms. I couldn't find a reference in the manual, but you can run "cvs --help-synonyms" for the full list. -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Problem: About repositiory
How about: A. checkout new working dir using new repository location B. transfer content of old working copy to new working copy C. delete and cvs remove files from new working copy if necessary D. get rid of old working copy and continue work in new working copy Erik Mike Ayers <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 11/05/2002 12:31 AM To: Noel Yap <[EMAIL PROTECTED]> cc: Xicheng Jia <[EMAIL PROTECTED]>, CVS <[EMAIL PROTECTED]> Subject:Re: Newbie Problem: About repositiory Noel Yap wrote: > There're several things (with varying pro's and con's) > you can do: > 1. move back the repo until you've checked in > everything you need (and don't checkout another > working directory until it's moved back) > 2. create a symlink (or mount the new repo) to the > location of the old repo > 3. modify all your CVS/R* files to point to the new > repo > > 1 and 2 may not be possible in your environment. 3 is > intrusive and error-prone. What about...? 4. Run a script which deletes all the CVS/Root directories and then `cvs -d /new/path/to/repository update` Won't this do the trick? /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: can't add with wincvs
Steve Buehler wrote: Ok. I was able to get a private key setup and running so that it logs me in. Now I am running into another problem. I can connect to the server. In fact, in WinCVS, I can even do a create which gives me the following reply in WinCVS: cvs init *CVS exited normally with code 0* WHOA, Nelly! Where's the `cvs checkout` that you MUST do between these two paragraphs? Even with no files in the repository, it will set up your CVS directory. Now. When I go again and click on a file to add (testz.php), then click on the "Add Selected" button, I get this: cvs add testz.php (in directory C:\ijobs\cvs\) cvs add: in directory .: cvs [add aborted]: *PANIC* administration files missing Sounds like it couldn't find the CVS directory... /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS, emacs, shh, cygwin
Seth Copen Goldstein wrote: I am having trouble using cvs, emacs, bash, etc. on my windows XP machine. My configuration is: CVS: Concurrent Versions System (CVS) 1.11 (client/server) Emacs: GNU Emacs 21.2.1 (i386-msvc-nt5.1.2600)\n of 2002-03-19 on buffy Cygwin: not sure version, cygwin1.dll is dated: 2/25/2002 Ssh: (from cygwin): OpenSSH_3.2.3p1, SSH protocols 1.5/2.0, OpenSSL 0x0090604f I have afs (version 1.2.2b), but would also be ok with using SSH. However: If I can't set a CVSROOT to :local:f:/path (it complains about path not being absolute) Correct. Cygwin is a Unix emulation layer, and therefore does not recognize DOS drive specifications. CVSROOT should be :local:/cygdrive/f/path. I can't set CVS_RSH=SSH, because cvs replies: cvs [checkout aborted]: end of file from server (consult above messages if any) This is probably an artifact of your bad CVSROOT, yes? (there are no error messages) Don't you get the bad CVSROOT error message? Wouldn't that count? /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
A silly problem: About co & ci
I am wondering if or not there is any difference between "co" and "checkout", also between "ci" and "commit"? Can anyone give me a hint. Thanks a lot, Good day, Xicheng ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: can't add with wincvs
Steve Buehler writes: > > Now. When I go again and click on a file to add (testz.php), then click on > the "Add Selected" button, I get this: > cvs add testz.php (in directory C:\ijobs\cvs\) > cvs add: in directory .: > cvs [add aborted]: *PANIC* administration files missing You can only do add when you're in a checked out directory. I strongly suggest you go to www.cvshome.org and read the CVS manual. -Larry Jones Hmph. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS, emacs, shh, cygwin
Seth Copen Goldstein writes: > > If I can't set a CVSROOT to :local:f:/path (it complains about path not > being absolute) If your CVS is from cygwin, you probably have to use a cygwin-style path (:local:/cygdrive/f/path) instead of a DOS-style path. > I can't set CVS_RSH=SSH, because cvs replies: > cvs [checkout aborted]: end of file from server (consult above messages if > any) > > (there are no error messages) > > Note: I can't get ssh to work either (it replies: setgid 1: Invalid > argument) If you can't get ssh to work, you can hardly expect CVS to work using it, now can you. I suggest asking a cygwin and/or ssh list instead of the CVS list. -Larry Jones Nobody knows how to pamper like a Mom. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
