Re: mobile CVS
Hello Geoff, * On Tue, Jul 20, 2004 at 04:57:30PM -0400 Geoff Beier wrote: I've handled this in the past by simply using a standard ssh client to connect to the appropriate server and port, and forwarding port 22 on localhost. *grmph* I use that approach myself for all kinds of stuff with ssh, but I never thought about using this for CVS. Thank you very much for giving the blockhead (me) a whack on the back of the head. ;-) Thank you very much, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ http://www.viceteam.org/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: mobile CVS
Hello Stephen, * On Tue, Jul 20, 2004 at 01:15:45PM -0700 Stephen Carville wrote: I use dfferent repository paths Internally: cvs -f -d :ext:[EMAIL PROTECTED]:/var/cvs checkput -P module Externally: cvs -f -d :ext:[EMAIL PROTECTED]:/var/cvs checkout -P module Well, these -d override whatever is written in CVS/Root, don't they? Anyway, I do not like to be forced to use a different command line parameter every time I'm accessing a repository. I find Geoff's solution much more handy. Anyway, thank you very much for your suggestion, too. Regards, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ http://www.viceteam.org/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Setting up a new CVSNT or Linux server ??
Hi all ! I am fairly new to the world of CVS (I come from the ClearCase world J) and am in the process of researching/setting up CVS for a small team of approx. 8 developers. I have briefly experienced WinCVS (Win2000) with a Linux CVS server in the past. I am looking into the options CVSNT for a server, or possibly Linux. Do you have any suggestions on which would be better and why, or any other suggestions? Thanks ! -PaN ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
how to update from the repo of a repo?
(apparently, my earlier post didn't get accepted due to timing of rejoining the list, so let's try it again.) is there an accepted way of setting up a CVS repo for a number of developers, where the repo itself is updated from yet another repo? (this might be the equivalent of BK's clone of a clone.) i want some developers to work with a kernel source tree, for which there's a CVS repo out there on the net that's updated on a regular basis. but i'd rather they didn't update from the main repo directly, i'd prefer them to update from a local repo i want to create, and it's the local repo that will update from the main one, just to keep everyone consistent. in addition, these developers will be making changes to the kernel source, and checking those changes back in for the benefit of the others. they definitely don't have the authority to check stuff back in to the main repo; hence, the need for a local repo. in short, i want to set up a local repo that will accept changes both as updates from the main, remote one, as well as commits from the local developers (obviously, watching for the times when they have to deal with conflicts along the way). thoughts? rday ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Setting up a new CVSNT or Linux server ??
At 09:01 AM 7/21/2004, Paul Nusbaum wrote: I am looking into the options CVSNT for a server, or possibly Linux. Well, on this list, you'll probably get recommendations for Linux. If you want a recommendation for CVSNT, just ask at [EMAIL PROTECTED] :-) But, it depends on a lot on your environment. Are you a Windows-only shop and expect to never use Linux (or Mac OS X, or Solaris, or many non-Unix type systems) for development? Then CVSNT is probably for you. If you will use any client that runs on something other than Windows, then you should probably strongly consider a Linux host. There's other reasons to consider a Linux or other Unix-type host, but watch out for religious arguments when you start talking about them. [Personally, I'm of the Unix-type persuasion.] Fred ___ Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Setting up a new CVSNT or Linux server ??
Paul Nusbaum wrote: I am 'fairly' new to the world of CVS (I come from the ClearCase world J) - and am in the process of researching/setting up CVS for a small team of approx. 8 developers. I have briefly experienced WinCVS (Win2000) with a Linux CVS server in the past. I am looking into the options - CVSNT for a server, or possibly Linux. Do you have any suggestions on which would be better and why, or any other suggestions? You're asking a list which primarily has UNIX users whether Linux or Windows is better, and you expect an unbiased opinion?!?! :=) Seriously, though, as far as I know, CVSNT and GNU CVS (by which I mean the version hosted out of cvshome.org) are equally capable servers. Are there specific features you require? For example, I don't know if CVSNT supports SSH. It does, however, support ssapi, which (AIUI) uses operating-system authentication to provide a similar level of protection. Another prime consideration is: which server platform would you rather set up and maintain, a *nix box, or a Windows box? If nobody in your department has any experience administering *nix, then Windows is probably your preferred platform. The preferred platform will pretty much dictate which version you use. Also keep in mind that whatever you choose today is not your final answer. If you later decide to switch server platforms, then moving the repository is a simple matter of copying the repository files from one server to another (be sure to use a binary mode transfer to avoid corrupting the repository). -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Setting up a new CVSNT or Linux server ??
Frederic Brehm wrote: But, it depends on a lot on your environment. Are you a Windows-only shop and expect to never use Linux (or Mac OS X, or Solaris, or many non-Unix type systems) for development? Then CVSNT is probably for you. Well, I'd actually modify that slightly: If you're a Windows-only shop and do not know how, or do not want, to maintain a Linux system, then use CVSNT. We're a Windows-only shop (well, OK, Windows and vxWorks, but that doesn't really count 'cause it can't be used as a CVS server ;-) but our CVS server is running on a UNIX box. We recently reviewed our version management strategy, and decided to stay with UNIX as a server. In my case, it was mostly out of a distrust of Microsoft as a server. Perhaps that mistrust is misplaced (I expect nobody on this list will argue the point, though ;=). If you will use any client that runs on something other than Windows, then you should probably strongly consider a Linux host. Now, just to be sure this doesn't come across as a religious-type argument, can you provide a reason for this recommendation? The only reason I can think of is a limitation on the protocols that CVSNT supports - but a quick glance at cvsnt.org seems to suggest that it supports at least pserver, ssh, and kerberos, and possibly other protocols. Oh, by the way - when I looked at cvsnt.org I noticed that there's a strong warning against downloading it if you live in a jurisdiction that regulates cryptographic imports. If you live in one of those jurisdictions, then I guess GNU CVS is the route to take. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Setting up a new CVSNT or Linux server ??
At 09:51 AM 7/21/2004, Jim.Hyslop wrote: If you will use any client that runs on something other than Windows, then you should probably strongly consider a Linux host. Now, just to be sure this doesn't come across as a religious-type argument, can you provide a reason for this recommendation? Filename case sensitivity. Fred ___ Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: how to update from the repo of a repo?
Robert P. J. Day [EMAIL PROTECTED] writes: is there an accepted way of setting up a CVS repo for a number of developers, where the repo itself is updated from yet another repo? (this might be the equivalent of BK's clone of a clone.) There is no standard way to transfer individual commit log entries etc between repositories, the most obvious method is to simply do a import onto a vendor branch on a regular basis. See the chapter on Tracking third-party sources in the manual for details. -- Brian Gough Network Theory Ltd, Publishing the CVS Reference Manual --- http://www.network-theory.co.uk/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: how to update from the repo of a repo?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robert P. J. Day [EMAIL PROTECTED] writes: is there an accepted way of setting up a CVS repo for a number of developers, where the repo itself is updated from yet another repo? (this might be the equivalent of BK's clone of a clone.) This is typically done by organizations such as FreeBSD, NetBSD and OpenBSD, by using cvsupd on the primary repository and cvsup to pull the mirror to the client from the master. Local changes are made by either creating a branch on the primary that will never be used on the primary, but instead dedicated to a particular secondary mirror, or by using the CVS_LOCAL_BRANCH_NUM environment variable set to a high even number like 2 and creating a new local branch for the secondary mirror repository. At such time that the local work is ready to be integrated, it would be committed to the primary by someone who is given permission to see both the secondary and the primary repositories directly. i want some developers to work with a kernel source tree, for which there's a CVS repo out there on the net that's updated on a regular basis. but i'd rather they didn't update from the main repo directly, i'd prefer them to update from a local repo i want to create, and it's the local repo that will update from the main one, just to keep everyone consistent. This sounds very much as if you are doing to be doing 'cvs import' to import snapshots of the primary repoistory into your secondary repository which is another method of accomplishing the same thing. The difference is that your secondary repository will not carry all of the log information of changes committed to the primary repository. in addition, these developers will be making changes to the kernel source, and checking those changes back in for the benefit of the others. they definitely don't have the authority to check stuff back in to the main repo; hence, the need for a local repo. This requirement should be possible to be met by either of the above methods. in short, i want to set up a local repo that will accept changes both as updates from the main, remote one, as well as commits from the local developers (obviously, watching for the times when they have to deal with conflicts along the way). thoughts? Figure out what you really want, but be careful as CVS does not have a simple way to merge deltas of branches from the primary repoistory into secondary branches in the same manner that BitKeeper deals with deltas. There must be a single repository that is the master for any given branch under CVS. -- Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFA/o6Y3x41pRYZE/gRAm4dAJ96ixjMzd0apYHjboxr6vXecRXfigCgo9wI Xo3F698KQkKZqjwkiwGasLQ= =Yqai -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Setting up a new CVSNT or Linux server ??
At 02:08 PM 7/21/2004, Jim.Hyslop wrote: OK, let's run through a use-case scenario: Scenario: Repository has a file named 'file'. User wants to 'cvs add File'. CVSNT server, Windows client: 'add' command ignored CVSNT server, UNIX client: 'add' command fails: File added independently by second party UNIX server, Windows client: add command ignored UNIX server, UNIX client: add and commit will succeed. In your scenario, it appears to me that the only failure comes with the CVSNT server and UNIX client. In that case, the user knows that there are two separate files file and File in the directory and CVS should be able to add both but it refuses. If I were that user, I would think CVS is broken. In all other cases, cvs add does the right thing, and another user will be able to recreate the sandbox of this user. So, the only problem comes when CVSNT is used as a server. Therefore, use a UNIX server. If you plan on sharing the same files between Windows and unix-like systems, then you have to make sure your filenames are OK on both systems. It doesn't matter if you use CVS to do the sharing, or if you send zipped directories back and forth. That's a problem that is independent of CVS. Fred ___ Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Setting up a new CVSNT or Linux server ??
Frederic Brehm wrote: At 02:08 PM 7/21/2004, Jim.Hyslop wrote: OK, let's run through a use-case scenario: Scenario: Repository has a file named 'file'. User wants to 'cvs add File'. CVSNT server, Windows client: 'add' command ignored CVSNT server, UNIX client: 'add' command fails: File added independently by second party UNIX server, Windows client: add command ignored UNIX server, UNIX client: add and commit will succeed. In your scenario, it appears to me that the only failure comes with the CVSNT server and UNIX client. Just because CVS does its job properly does not mean that there is no failure. In this scenario, assuming a mixed-platform project, there are actually two distinct failures: one where CVS issues an error message; and another where the tool itself did not fail, but there was a violation of the larger configuration management picture. So, the only problem comes when CVSNT is used as a server. Therefore, use a UNIX server. No, there is also the problem when CVSNT is used as a server, and a UNIX user forgets, ignores or blatantly breaks the project rules around file names. If you plan on sharing the same files between Windows and unix-like systems, then you have to make sure your filenames are OK on both systems. True, but if all else is equal, and you have a choice between a tool that allows you to break the rule, and a tool that enforces the project rule, isn't it much better to eliminate the human factor and choose the tool that can help enforce that rule? -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Multi-tier development CVS plan
adp [EMAIL PROTECTED] wrote: Did you get a response on this? We are looking to move from a single CVS branch (MAIN) to either a two- or three-tiered system. Would be happy with hints. We are thinking of this: unstable - stable - release The usual way to handle this on CVS is an unstable trunk with stable+release branches. ++unstable \\ \stable1-|-| \ rel-1.1 rel-1.2 \ \---stable2---|- rel-2.1 Every time your unstable trunk reaches a milestone, you cut a stabilization branch. On this branch you perform only cleanups and add no new features. Eventually you tag your stabilization branch and cut a release, after which the branch becomes a bugfix branch. Promoting a new batch of changes from unstable to stable is done by starting a new stable branch. Not shown on the diagram is how the bugfixes from maintained release branches would be merged to later releases and to the trunk, but that's standard CVS fare. You *might* make the original promotion model work in CVS with floating tags: cvs tag -F -r1.6 STABLE toto.c --oops no, cvs tag -F -r1.5 STABLE toto.c etc. You could then check out with the -rSTABLE flag to get an official stable tree without the unstable riff-raff. That said, I don't understand the promotion model well enough to give you sound advice. To recap: unstable: This is where our current development goes. The trunk, also the default. stable: This is where we merge our soon-to-be-released code so that QA can begin work. You don't really merge in the CVS sense, instead you fork a branch to isolate changes on it from the unstable trunk. release: This is where we merge from stable, tag an official code release, and then push the release. You could branch the stable branch, but ususually it's easier to just tag milestones on it. ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Setting up a new CVSNT or Linux server ??
Frederic Brehm [EMAIL PROTECTED] wrote: [ case-sensitive client with case-insensitive server] In your scenario, it appears to me that the only failure comes with the CVSNT server and UNIX client. In that case, the user knows that there are two separate files file and File in the directory and CVS should be able to add both but it refuses. But allowing the add would be worse for the developers on case-insensitive clients. For them, the next update would yield endless messages to move File, it is in the way. ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
