Re: Nubie question
Dmitry Suzdalev wrote: But what if i dont know this name? Can I find it somehow? Is there a CVS command that lists all tag names? cvs stat -v or cvs log -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Nubie question
Dmitry Suzdalev writes: But what if i dont know this name? Can I find it somehow? Is there a CVS command that lists all tag names? Both cvs [r]log and cvs status -v can be used to list the tags on a file. -Larry Jones If I get a bad grade, it'll be YOUR fault for not doing the work for me! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
tag vs rtag question, was Re: Merging from vendor-branch to branch
Nick Patavalis wrote: SNIP You merge the local changes cvs co -j VENDOR_R1 -j VENDOR_R2 module You resolve the confilicts, test the new sources, and generaly make sure that everything is stable. Then commit your changes. Several commits may be necesairy since the conflict resolution may take some time. No problem though since the rest of the developers are safely isolated in the VENDOR_R2_MERGE branch). When you have finished with the conflict resolution and tests you tag the trunk accordingly cvs rtag VENDOR_R2_MERGED SNIP I have not worked with normal branches or rtag before, I have always used tag and import, so I am asking this from a 'please correct my head perspective'. If at the point the rtag is ran above the last commit of a file happened on the branch would rtag place the tag on the HEAD version of the file (what we want here, I think) or on the branch version of the file? http://www.cvshome.org/docs/manual/cvs_4.html#SEC44 http://www.cvshome.org/docs/manual/cvs_17.html#SEC153 The above pages from the manual are not real clear (to me) on what rtag tags if you do not give a -rsomthing as it is working on some (possibly unknown) state of the repository. Even -D seems a little scary unless you have spent enough time looking in the repository to verify that, at the time specified, the baseline is consistent. I would think that with the situation above, doing a cvs tag VENDOR_R2_MERGED in the working directory where conflict resolution was finished would be the safest method, to be sure you tagged the resolved files and not something else. Thanks for any clue sticks. -- I'd crawl over an acre of 'Visual This++' and 'Integrated Development That' to get to gcc, Emacs, and gdb. Thank you. -- Vance Petree, Virginia Power ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: tag vs rtag question
On Wed, Oct 23, 2002 at 01:49:36PM -0500, Todd Denniston wrote: Nick Patavalis wrote: You merge the local changes cvs co -j VENDOR_R1 -j VENDOR_R2 module You resolve the confilicts, test the new sources, and generaly make sure that everything is stable. Then commit your changes. Several commits may be necesairy since the conflict resolution may take some time. No problem though since the rest of the developers are safely isolated in the VENDOR_R2_MERGE branch). When you have finished with the conflict resolution and tests you tag the trunk accordingly cvs rtag VENDOR_R2_MERGED If at the point the rtag is ran above the last commit of a file happened on the branch would rtag place the tag on the HEAD version of the file (what we want here, I think) or on the branch version of the file? The tag will be placed on the most recent revision of the trunk (i.e the HEAD). ...Though I also have some confused ideas about what exactly HEAD means. Could please a CVS guru give us a precise *definition* of what the HEAD tag is? I would think that with the situation above, doing a cvs tag VENDOR_R2_MERGED in the working directory where conflict resolution was finished would be the safest method, to be sure you tagged the resolved files and not something else. True! /npat -- flowchart, v.: To obfuscate (a problem) with esoteric cartoons. -- Stan Kelly-Bootle ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: tag vs rtag question
I would think that with the situation above, doing a cvs tag VENDOR_R2_MERGED in the working directory where conflict resolution was finished would be the safest method, to be sure you tagged the resolved files and not something else. On the other hand, if you have *deleted* a file, cvs tag won't tag the repository file. This can lead to interesting file reappearing in my workarea problems when others update to the tag.. Tough call. I used to do merges late in the day when concurrent checkins were unlikely. -- Shankar. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: tag vs rtag question
On Wed, Oct 23, 2002 at 01:58:27PM -0700, Shankar Unni wrote: I would think that with the situation above, doing a cvs tag VENDOR_R2_MERGED in the working directory where conflict resolution was finished would be the safest method, to be sure you tagged the resolved files and not something else. On the other hand, if you have *deleted* a file, cvs tag won't tag the repository file. This can lead to interesting file reappearing in my workarea problems when others update to the tag.. Can you elaborate a bit on this? You mean deleted by the developers while working in the branch, or while doing conflict resolution in the trunk? /npat -- Dijkstra probably hates me -- Linus Torvalds, in kernel/sched.c ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: tag vs rtag question
Oh, back at my previous employer, we had a branched development tree, and used to merge from the branch into the mainline on a regular basis. After each merge, we would tag the last version merged into mainline on the branch, and use that as the base for the cvs update -j the next time around. The problem was, if one of the files was *deleted* on the branch, cvs tag wouldn't move the tag for that file - you'd have to use cvs rtag for it. The developer in question had done separate cvs rms on the mainline and the branch, but since the deleted version on the branch wasn't tagged, when I did the next merge from the branch to the mainline, the deleted file reappeared. Anyway, the bottom line was to *carefully* use cvs rtag.. -Original Message- From: Nick Patavalis [mailto:npat;inaccessnetworks.com] Sent: Wednesday, October 23, 2002 2:13 PM To: Shankar Unni Cc: 'CVS-II Discussion Mailing List' Subject: Re: tag vs rtag question On Wed, Oct 23, 2002 at 01:58:27PM -0700, Shankar Unni wrote: I would think that with the situation above, doing a cvs tag VENDOR_R2_MERGED in the working directory where conflict resolution was finished would be the safest method, to be sure you tagged the resolved files and not something else. On the other hand, if you have *deleted* a file, cvs tag won't tag the repository file. This can lead to interesting file reappearing in my workarea problems when others update to the tag.. Can you elaborate a bit on this? You mean deleted by the developers while working in the branch, or while doing conflict resolution in the trunk? /npat -- Dijkstra probably hates me -- Linus Torvalds, in kernel/sched.c ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: tag vs rtag question
On Wed, Oct 23, 2002 at 02:24:47PM -0700, Shankar Unni wrote: The problem was, if one of the files was *deleted* on the branch, cvs tag wouldn't move the tag for that file - you'd have to use cvs rtag for it. The developer in question had done separate cvs rms on the mainline and the branch, but since the deleted version on the branch wasn't tagged, when I did the next merge from the branch to the mainline, the deleted file reappeared. Oh, I see. You mean that you were using the *same* tag-name and you were just pushing it forward to more recent revisions, and that this didn't behave well when the push was crossing a delete operation! Tricky, indeed! /npat -- Don't ever think you know what's right for the other person. He might start thinking he knows what's right for you. -- Paul Williams, `Das Energi' ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
question regarding file has disappeared message on checkout..
Does anyone know what this means? I'm getting this message on a few files when I do a checkout .. It looks like the files in question are still available in the repository, but they did not get checked out... Thanks in advance for any help! markl ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: modules file question
All, Feel free to disregard my previous e-mail (below). I answered my own question with some experimentation. It looks like using alias modules with the -a flag and a space-delimited list of paths will get me what I need. Matt -Original Message- From: Matt Lyon Sent: Monday, October 14, 2002 5:18 PM To: Info-Cvs (E-mail) Subject: modules file question Hi, After reviewing the documentation, I'm a bit confused as to whether or not an alias module can contain multiple aliases or directories in some sort of delimited list. Consider the following two examples: (1) Alias module definition: admin com/stargus/ui,com/stargus/platform/admin,com/stargus/platform/framework/admin,com/stargus/starnode/admin (2) Ampersand module definition: ui com/stargus/ui platform_admin com/stargus/platform/admin framework_admin com/stargus/platform/framework/admin starnode_admin com/stargus/starnode/admin admin ui platform_admin framework_admin starnode_admin Obviously example 1 is simpler, but the documentation leads me to believe that example 2 is the only viable approach to achieve what I need to do. However, the documentation is a bit ambiguous, because it suggests, aliases may contain either other module names or paths. The pluralization of aliases in the manual is what piqued my curiosity; since I'm using paths, is there a way to specify multiple paths for one alias module with some sort of delimiter like a space or comma between them? 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
modules file question
Hi, After reviewing the documentation, I'm a bit confused as to whether or not an alias module can contain multiple aliases or directories in some sort of delimited list. Consider the following two examples: (1) Alias module definition: admin com/stargus/ui,com/stargus/platform/admin,com/stargus/platform/framework/admin,com/stargus/starnode/admin (2) Ampersand module definition: ui com/stargus/ui platform_admin com/stargus/platform/admin framework_admin com/stargus/platform/framework/admin starnode_admin com/stargus/starnode/admin admin ui platform_admin framework_admin starnode_admin Obviously example 1 is simpler, but the documentation leads me to believe that example 2 is the only viable approach to achieve what I need to do. However, the documentation is a bit ambiguous, because it suggests, aliases may contain either other module names or paths. The pluralization of aliases in the manual is what piqued my curiosity; since I'm using paths, is there a way to specify multiple paths for one alias module with some sort of delimiter like a space or comma between them? Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Commit question
Is there a way to commit a change to a version without first having to check it out to your workstation? Thanks for any help. __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Commit question
Pat Young writes: Is there a way to commit a change to a version without first having to check it out to your workstation? No. You could import it, but that probably isn't what you want. -Larry Jones Oh, now YOU'RE going to start in on me TOO, huh? -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Newbie connection question
Hi All, I'm still reading some of the documentation but want to get feedback from my system that the pieces are working. I saw a previous answer to a connection question and tried it on my newly installed CVS/CVSNT system (most recent stable releases). I tried the following in a Command window on my Win2000ProSP3 (which, incidentally,hosts CSVNT): 11:37 I:\telnetMy2000Server 2401 Connecting To My2000Server...Could not open a connection to host on port 2401 : Connect failed 11:37 I:\ where "My2000Server"represents the name of my Win2000AS-SP3 advanced server hosting CVS. I substituted the server's IP address for the server name and got essentially the same response. I think I set up CVS for something like NT authentication or Domain authentication. I definitely did not choose pserver authentication. I kept the default port assignment, so 2401 sounds right to me. I am logged on my workstation as a Domain Administrator. Ultimately , I'd like to know the simplest way to test whether the CVSNT-CVS hookup is working. TIA, Richard
Newbie question : common/shared objects
I'm quite new to using CVS. Our applications rely on common source, and built products alike. Some of these are 3rd party (dlls, jars, source, etc.) and some are internally developed. For instance, to build release 1.2 of product X, I need release 3.4 of product A, release 5.4 of product B, and release 1.1 of product C. To build release 2.1 of Product Y, I will use release 3.4 of product A, release 5.3 of product B, and release 2.0 of product D. How is this typically handled within CVS? TIA, Jay ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie question : common/shared objects
At 10:15 AM 9/26/2002, Jay Yarbrough wrote: To build release 2.1 of Product Y, I will use release 3.4 of product A, release 5.3 of product B, and release 2.0 of product D. How is this typically handled within CVS? Make each product a separate module. Then you can tag each release of each product and export them independently. Here's a way to build your product Y: Keep each released version of every product in some well-known place. This goes for third party products as well as your internal products. For example, build release 3.4 of product A and put it in /company/product/V3_4/A.zip or something like that. To create a release of product Y, your build procedure can use the released versions of the products it depends on. There doesn't have to be a distinction here between your internal products and third party products because they are all referenced in a similar manner. Fred ___ Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie question : common/shared objects
Jay Yarbrough wrote: I'm quite new to using CVS. Our applications rely on common source, and built products alike. Some of these are 3rd party (dlls, jars, source, etc.) and some are internally developed. For instance, to build release 1.2 of product X, I need release 3.4 of product A, release 5.4 of product B, and release 1.1 of product C. To build release 2.1 of Product Y, I will use release 3.4 of product A, release 5.3 of product B, and release 2.0 of product D. How is this typically handled within CVS? TIA, Jay Two ways I see. 1. for the crowd who believe 0 binary files should be stored in CVS a) put everything you have source for under cvs, probably good to have a separate module for each of the 3rd party sources. b) store all binaries in an accessible directory (use naming to indicate binary version). c) build either a file describing which binaries go with the version, or build a makefile (or your build tool of choice) which will get the binaries needed for the version. d) check the makefile/binary description file into the repository. e) use cvs tag or cvs rtag to apply the same tag to the whole set of cvs modules for the version, including the makefile/binary description file. to retrieve a version a) cvs checkout -r $TAGNAME all_modules b) use makefile/binary description file to recover needed binary files. c) build 2. for the crowd that tolerates binary files in CVS, and understands that the ',v' files will get big quick. a) put everything you have source for under cvs, probably good to have a separate module for each of the 3rd party sources. b) put binaries you do not have source for under cvs (don't forget `-kb') http://www.cvshome.org/docs/manual/cvs_9.html#SEC80 c) use cvs tag or cvs rtag to apply the same tag to the whole set of cvs modules for the version. Remember to omit ones not needed. to retrieve a version a) cvs checkout -r $TAGNAME all_modules b) build -- I'd crawl over an acre of 'Visual This++' and 'Integrated Development That' to get to gcc, Emacs, and gdb. Thank you. -- Vance Petree, Virginia Power ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie question : common/shared objects
Jay Yarbrough wrote: I'm quite new to using CVS. Our applications rely on common source, and built products alike. Some of these are 3rd party (dlls, jars, source, etc.) and some are internally developed. For instance, to build release 1.2 of product X, I need release 3.4 of product A, release 5.4 of product B, and release 1.1 of product C. To build release 2.1 of Product Y, I will use release 3.4 of product A, release 5.3 of product B, and release 2.0 of product D. How is this typically handled within CVS? It isn't. It's a configuration management problem, CVS is an archiving system. Because configuration management and archiving are so tightly linked in practice, people tend to miss the fact that they're conceptually separate. I am, unfortunately, not terribly familiar with available CM tools. Many folk seem to be happy with simple homegrown CM models, and I see a couple of suggestions have already been forwarded. I just wanted you to be aware that whatever solution you pursue, you should be able to use CVS to do the archiving. /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
question about $log$ and merging
A colleague and I just went through a miserable branch-to-head merge, and I'm looking for some help to avoid this in the future. According to the CVS docs (http://www.cvshome.org/docs/manual/cvs_12.html#SEC103): 12.5 Problems with the $Log$ keyword. ... A more serious concern is that CVS is not good at handling $Log$ entries when a branch is merged onto the main trunk. Conflicts often result from the merging operation. We're running into this exact problem. We just merged from a branch back onto the trunk this morning, but got a ton of merge conflicts - all of them having to do with the $Log$ keyword. None of the -k substitution options are fixing the problem (-ko, -kk) - and they're even causing more problems, since they whack the -kb status that binary files have. Anyone know of any workarounds to this situation? I tried to google on this topic, but all I kept coming up with were the same links into the CVS documentation that's online on a billion different sites on the Net. TIA! DR ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: question about $log$ and merging
On Thu, 19 Sep 2002, David Rosenstrauch wrote: We're running into this exact problem. We just merged from a branch back onto the trunk this morning, but got a ton of merge conflicts - all of them having to do with the $Log$ keyword. None of the -k substitution options are fixing the problem (-ko, -kk) - and they're even causing more problems, since they whack the -kb status that binary files have. Anyone know of any workarounds to this situation? The workaround is to delete $Log$ from all your files, along with all the crap it has ever generated. Then commit. Treat any conflict within a $Log$-generated text area as irrelevant; just blow away the whole section including the conflict. The $Log$ keyword is next to useless, because all it does is reproduce information that is already available in the repository. Unless the commit messages are conscientiously written, they are unlikely to be of value to anyone, and even if they are so written, they won't be of use to anyone who has no access to the repository, because they describe changes recorded in inaccessible past versions. You need access to the old versions to fully comprehend what the messages are talking about. Lastly, you want an integrated log of changes for the project or module as a whole; so learn to maintain ChangeLog files. A bunch of expanded $Log$'s scattered in a file tree is useless compared to a well-maintained ChangeLog. I've worked with people who insisted on $Log$ as a policy; it was frustrating dealing with the merge problems. None of these people understood or performed the merges. If some goofball insists on $Log$, make him do all the merges for a month. ;) ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
VSS to CVS perl script question
I'm trying to move a project from my VSS repository to CVS. This project has multipule sub-dirs but after running the script it only created the first level directory and not all the sub dirs. What am I missing? I made sure I have vsions of rm and chmod that support -R option. It did go on checking the sub dirs but I got the following messages: Syncing html2index.exe * cvs server: nothing known about html2index.exe html2index.exe is not an existing filename or projec Syncing hwlib.chm * cvs server: nothing known about hwlib.chm hwlib.chm is not an existing filename or project Syncing hwlib.hhc * cvs server: nothing known about hwlib.hhc hwlib.hhc is not an existing filename or project Syncing hwlib.hhk * cvs server: nothing known about hwlib.hhk hwlib.hhk is not an existing filename or project Syncing hwlib.hhp * cvs server: nothing known about hwlib.hhp hwlib.hhp is not an existing filename or project Syncing hwlibdoc.c * cvs server: nothing known about hwlibdoc.c hwlibdoc.c is not an existing filename or project Syncing master.xre * cvs server: nothing known about master.xre master.xre is not an existing filename or project Syncing ReadMe.txt * cvs server: nothing known about ReadMe.txt ReadMe.txt is not an existing filename or project Syncing run.bat * cvs server: nothing known about run.bat run.bat is not an existing filename or project Syncing config.h * cvs server: nothing known about config.h config.h is not an existing filename or project Syncing mpegcmn.h * cvs server: nothing known about mpegcmn.h mpegcmn.h is not an existing filename or project Syncing mpegerr.h * cvs server: nothing known about mpegerr.h mpegerr.h is not an existing filename or project And the checkins stopped? What happened? Matt The RE Guy __ Do you Yahoo!? Yahoo! News - Today's headlines http://news.yahoo.com ___ 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
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
question about importing
After the original import, why do you have to give the full path in the repository to where the imported files are to do? Is it because an import assumes nothing even when there are CVS directories? I ask because I just did the second import of vendor code and the result was not what I expected. Here's what I did (note: EQC is a directory under /export/cvsroot/SystemaRelease2.1): cvs import -I ! -I CVS -m Import of Version 2.1.22 EQC Systema Version_2-1-22 and it created an EQC directory on the same level as SystemaRelease2.1 Removed that offending EQC directory from the repository and did this command: cvs import -I ! -I CVS -m Import of Version 2.1.22 SystemaRelease2.1/EQC Systema Version_2-1-22 and this did what I wanted. I just wanted to understand the why. TIA, Jeanie __ This is Linux country. On a quiet night, you can hear NT re-boot. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: question about importing
On Mon, Sep 09, 2002 at 11:17:12AM -0700, Schwenk, Jeanie wrote: After the original import, why do you have to give the full path in the repository to where the imported files are to do? Is it because an import assumes nothing even when there are CVS directories? Correct. An import of a tree with CVS directories is just like an import of one without. (The CVS stuff isn't even a special enough case to get forcibly ignored; as you've noticed, it's just on the default ignore list like *.o etc.) This is reasonable, given the command's name. Even if there is CVS metadata, a command for importing stuff ought not to assume it relates to your repo. E.g. it could be that you checked out an open-source project over the Net, and you're importing the code into your own repo to track your local patches. Just because cvshome.org calls a particular module ccvs doesn't mean you want to use that name :-) import could arguably pay attention to the modules file -- but I'm not going to be the one to argue for it :-) since (a) I don't know what pay attention to would mean in practice, and (b) I rarely use the modules file anyway. -- | | /\ |-_|/ 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
Re: question about importing
Eric, At 02:39 PM 9/9/2002 -0400, Eric Siegerman wrote: import could arguably pay attention to the modules file -- but I'm not going to be the one to argue for it :-) since (a) I don't know what pay attention to would mean in practice, and (b) I rarely use the modules file anyway. If you don't use modules file, how do you get the list of modules in the repo w/o going to the repo manually and browsing what folders are there? cvs checkout -c returns just the modules file contents, or not? Stan Berka Stan Berka Programmer Annalyst Portland, OR Pope Talbot (503) 552-4315Fax (503) 2202726 ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: question about importing
Schwenk, Jeanie writes: After the original import, why do you have to give the full path in the repository to where the imported files are to do? Is it because an import assumes nothing even when there are CVS directories? When there are CVS directories where? In the directory you're importing, the repository, or somewhere else? If there are CVS directories in the directory you're importing, and they're from your repository, you should probably be using add rather than import. -Larry Jones I've got to start listening to those quiet, nagging doubts. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: question about importing
This is regarding a vendor branch. When the vendor sends us a new version, we import rather than add. This is per Cederqvist 13.2 Updating with the import command and Chapter 6 Tracking Third-Party Sources: Vendor Branches in Fogel's book. Perhaps I have misunderstood what these two instruct. I thought I had to have the vendor branch checked out. This is wrong? There are CVS directories because we have checked out the latest version vendor code. Over that we unjared the source jars the vendor sent into those very same directories. Then we run 1) the import command, 2) the merge command and 3)the commit command. Since add is not recursive, using add would be error prone not to mention very time consuming. Are we just supposed to unjar the source files into a new directory and run the import command? Jeanie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, September 09, 2002 12:03 PM To: Schwenk, Jeanie Cc: [EMAIL PROTECTED] Subject: Re: question about importing Schwenk, Jeanie writes: After the original import, why do you have to give the full path in the repository to where the imported files are to do? Is it because an import assumes nothing even when there are CVS directories? When there are CVS directories where? In the directory you're importing, the repository, or somewhere else? If there are CVS directories in the directory you're importing, and they're from your repository, you should probably be using add rather than import. -Larry Jones I've got to start listening to those quiet, nagging doubts. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: question about importing
On Mon, 9 Sep 2002, Stan Berka wrote: At 02:39 PM 9/9/2002 -0400, Eric Siegerman wrote: import could arguably pay attention to the modules file -- but I'm not going to be the one to argue for it :-) since (a) I don't know what pay attention to would mean in practice, and (b) I rarely use the modules file anyway. If you don't use modules file, how do you get the list of modules in the repo w/o going to the repo manually and browsing what folders are there? Ah, but this is only trivial use of the modules file, since you aren't actually composing modules hierarchically, but only making their names visible. Using modules in any other way will eventually bring harm upon you, for several reasons. The module structure is not versioned as part of your project (of course, the CVSROOT/modules file is subject to version control, but that is not quite the same thing). This is the big problem; if you restructure the project by rearranging the modules file, the change affects the old checkouts, which will conform to the new shape, thereby destroying any notion of configuration management. Other problems: CVS update does not notice changes to the modules file. If you add a sub-module, nobody can pick it up via update; the other users must check out. The wrong pathnames are reported in some situations. For example, try doing a cvs rdiff over a hierarchically composed module. The pathnames in the resulting patch are useless, and so you have a broken patch, one that can only be applied by someone who manually checks out the constitutent modules side by side. cvs checkout -c returns just the modules file contents, or not? That is nearly correct; the contents are subject to some reformatting, which allows for easier parsing of the output. -- Meta-CVS: directory structure versioning; versioned symbolic links; versioned execute permission; versioned property lists; easy branching and merging and third party code tracking; all implemented over the standard CVS command line client -- http://freshmeat.net/projects/mcvs ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: question about importing
Schwenk, Jeanie writes: This is regarding a vendor branch. When the vendor sends us a new version, we import rather than add. This is per Cederqvist 13.2 Updating with the import command and Chapter 6 Tracking Third-Party Sources: Vendor Branches in Fogel's book. Perhaps I have misunderstood what these two instruct. I thought I had to have the vendor branch checked out. This is wrong? Yes, it is. You do *NOT* want to have the vendor branch checked out. Are we just supposed to unjar the source files into a new directory and run the import command? Exactly. Importing the second (or third, or fourth, etc.) time is exactly like importing the first time except that you specify a different release tag. You should specify exactly the same repository directory and vendor tag as the first time, and you should import from a new directory, not a CVS working directory. -Larry Jones This sounds suspiciously like one of Dad's plots to build my character. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: question about importing
On Mon, Sep 09, 2002 at 11:54:14AM -0700, Stan Berka wrote: At 02:39 PM 9/9/2002 -0400, Eric Siegerman wrote: [...] I rarely use the modules file anyway. If you don't use modules file, how do you get the list of modules in the repo w/o going to the repo manually and browsing what folders are there? ls /Repos suits me fine. cvs checkout -c returns just the modules file contents, or not? Pretty much. So I don't consider it very useful. I didn't even know it existed until someone here asked me about it (or rather its GUI equivalent in TortoiseCVS) a week or two ago. -- | | /\ |-_|/ 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
RE: question about importing
Larry, Thank you for making importing clear. Jeanie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, September 09, 2002 12:28 PM To: Schwenk, Jeanie Cc: [EMAIL PROTECTED] Subject: Re: question about importing Schwenk, Jeanie writes: This is regarding a vendor branch. When the vendor sends us a new version, we import rather than add. This is per Cederqvist 13.2 Updating with the import command and Chapter 6 Tracking Third-Party Sources: Vendor Branches in Fogel's book. Perhaps I have misunderstood what these two instruct. I thought I had to have the vendor branch checked out. This is wrong? Yes, it is. You do *NOT* want to have the vendor branch checked out. Are we just supposed to unjar the source files into a new directory and run the import command? Exactly. Importing the second (or third, or fourth, etc.) time is exactly like importing the first time except that you specify a different release tag. You should specify exactly the same repository directory and vendor tag as the first time, and you should import from a new directory, not a CVS working directory. -Larry Jones This sounds suspiciously like one of Dad's plots to build my character. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie question
From: Eric Siegerman [mailto:[EMAIL PROTECTED]]
http://www.mail-archive.com/info-cvs%40gnu.org/msg21543.html
and my reply to that message.
Now that's the most useful post I've seen since I subscribed. A link to a
_searchable_ archive. The one linked from the bottom of every message is
unsearchable. Thank you!
Of course...
void ponderProblem() {
printf( New subscribers won't get this message, );
printf( so they won't be able to search for it );
printf( in the archives, so... );
ponderProblem();
}
Anyway the [EMAIL PROTECTED] link can be added to the
listserv Welcome message?
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
a question about defining modules
Hi folks, I tried the following line in CVSROOT/modules: foo-1.0-a -r Release-1-0-branch foobar in hope that when I 'co foo-1.0', I'd get the Release-1-0-branch branch, since I had thought that CVS would do a simple textual substitution on alias modules, but it turned out not. My situation is: 3 projects, A, B and C, share a common library X. They all need to make changes to libX, so I forked 3 branches from libX main trunk: branch-A, branch-B and branch-C. The result is every time I 'co A', I'd also 'co -r branch-A libX'. Some simple client-side scripting will facilitate the process, but I don't wanna handle the varieties of my team members' platforms, thus I hope to find some server-side trick to do it. Any hint or suggestion is greatly appreciated ;) Clay -- Isaac Claymore /\ASCII Ribbon Campaign Dawning Inc.\ /Respect for open standards Beijing, China X No HTML/RTF in email http://www.dawning.com.cn / \No M$ Word docs in email ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: a question about defining modules
At 04:04 AM 8/27/2002, Isaac Claymore wrote: My situation is: 3 projects, A, B and C, share a common library X. They all need to make changes to libX, so I forked 3 branches from libX main trunk: branch-A, branch-B and branch-C. Any hint or suggestion is greatly appreciated ;) Clay, CVS doesn't work very well as a configuration management tool. Use CVS to save your source code. Use something else (configure, perhaps) to configure the source to match the needs of the product during a build. Fred ___ Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: a question about defining modules
Message: 4 Date: Tue, 27 Aug 2002 07:52:40 -0400 To: Isaac Claymore [EMAIL PROTECTED],[EMAIL PROTECTED] From: Frederic Brehm [EMAIL PROTECTED] Subject: Re: a question about defining modules At 04:04 AM 8/27/2002, Isaac Claymore wrote: My situation is: 3 projects, A, B and C, share a common library X. They all need to make changes to libX, so I forked 3 branches from libX main trunk: branch-A, branch-B and branch-C. Any hint or suggestion is greatly appreciated ;) Clay, CVS doesn't work very well as a configuration management tool. Use CVS to save your source code. Use something else (configure, perhaps) to configure the source to match the needs of the product during a build. Fred Fred: Any recommendations on documentation other than man configure to figure out how to use configure? thanks. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: a question about defining modules
Any recommendations on documentation other than man configure to figure out how to use configure? bleah: http://www.gnu.org/directory/autoconf.html so-so: http://www.amazon.com/exec/obidos/asin/1565921127 better: http://www.amazon.com/exec/obidos/ASIN/1578701902 I'd be interested if others have better suggestions... ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Deployment Question
On Sun, Aug 18, 2002 at 10:37:53AM -0400, David Morsberger wrote: We are looking for a good way to merge the changes we make at the customer location with the development baseline at our facility. [without the ability to access the dev. repo from there] We currently create a branch (rel_sitex) and and deliver a tarred up cvsroot. If the per-customer changes you make are small enough that you can live without using CVS while on site, make the branch as you do now; but instead of delivering a copy of the repo to the customer, deliver a CVS sandbox checked out (not exported) on the branch. Then when it's time to bring the changes back, just tar up the (modified) sandbox and bring it back to your site. You should be able to commit without any conflicts, as no other activity should have happened on the branch; then merge the branch back into the baseline -- which may well produce conflicts, but at that point the deployment complexity has been smoothed over, leaving you with a straight-ahead merge. If you do need to do commits while at the customer's site ... I've been faced with a similar situation, but that was five or six years ago. I'd have to think more about how I handled it. It may well have involved imports, as you're contemplating -- but then again, maybe not. So if this is what you're after, let me know. Alternatively, see the recent sync repository thread, wherein a possible approach was discussed. -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / Anyone who swims with the current will reach the big music steamship; whoever swims against the current will perhaps reach the source. - Paul Schneider-Esleben ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Deployment Question
We management our software baseline using CVS. The development process is very standard but the deployment process is not. We normally have to make numerous changes to our baseline to fit within the customers infrastructure. The locations where we deploy our software do not have access to our CVS server. We are looking for a good way to merge the changes we make at the customer location with the development baseline at our facility. We currently create a branch (rel_sitex) and and deliver a tarred up cvsroot. We then checkout the files from the branch at the customer facility. We then try to merge the baselines together at our facility. We have tried numerous ways (replacing cvsroot, manually merging, ...) We are in the process of evaluating the idea of treating the new software as a vendor import. The questions are: Are we on the right track for merging the baselines? Is there a better way to merge the baselines? I am sure we are not the first ones to run into this problem. Thanks, Dave ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Quick 'how to' question about modules ...
Not sure if this is possible or not, and would appreciate a pointer to a doc if it is ... I have three modules: moduleA bin/moduleB bin/moduleC I'd like to make an 'alias' or something that, if I check out moduleA, it will include B and C as subdirectories. ie: moduleA/src/bin/moduleB moduleA/src/bin/moduleC is this possible? so far, I haven't found anything that says it is, so it just may be wishful thinking ... but figured I'd ask ... ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
a question about loginfo commit emails
Folks, I'm planning to set up CVSROOT/loginfo to deliver commit emails. After reading 'info cvs', I found that cvs provides stuffs like %svV to access file name and revision information of a commit operation. I'd love to include the log message, i.e. what '-m' specifies in a 'cvs commit', in commit mails, but cannot figure out how to retrieve that information. Have I missed anything? Or, is there any other trick? Thanks. -Clay ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: a question about loginfo commit emails
Isaac Claymore wrote: I'd love to include the log message, i.e. what '-m' specifies in a 'cvs commit', in commit mails, but cannot figure out how to retrieve that information. The commmit message is passed to the script via STDIN. -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie CVS commitinfo question
Greg A. [EMAIL PROTECTED] (Greg A. Woods; Planix, Inc.) writes: [ On Friday, July 12, 2002 at 16:54:15 (-0700), Bryan Bunch wrote: ] So my initial thought is why shouldn't the same user that has a global lock on the whole repository also be able to execute read-only operations like update or checkout that don't modify the repository's state? My guess is that it's simply easier to do lock management if locks aren't same-user-re-entrant and no other cvs operations are allowed once the commit starts. What does user identity have to do with repository integrity? The repoisitory is not likely in a consistent state when it's locked. It doesn't matter who locked it or who's trying to access it. Exactly. The right solution to the problem is to enhance CVS's locking to allow read locks to be upgraded to write locks and write locks downgraded to read locks. That way, long-running processes can take out read locks to ensure the tree stays consistent without locking out other users except when actively updating RCS files. -Larry Jones I think grown-ups just ACT like they know what they're doing. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: A not-so-CVS question
yup, and you can even point the .htaccess to read the CVS password file , so your users only have 1 password to remember for each repository they need to access. Beto Lee Fellows wrote: On Wed, 2002-07-10 at 06:06, Isaac Claymore wrote: Hi, CVS folks. My question is not strictly related to CVS itself, but I think this list is the right place to ask. I've set up ViewCVS for my team, but then everyone on our LAN gets read access to the repository through it, which is not desired. So is there any tool or mechanism that's able to add authentication functionality to ViewCVS without hacking its code? Or, do you folks have similar experience? Thanks~~ -Clay If you are using apache as the web server, have you looked at .htaccess and .htpasswd? ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs -- Norberto Meijome If you were supposed to understand it, we wouldn't call it 'code'. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie CVS commitinfo question
[ On Friday, July 12, 2002 at 16:54:15 (-0700), Bryan Bunch wrote: ] Subject: Newbie CVS commitinfo question I have a quick question about using the commitinfo admin file to perform a source-file check before commiting. Mabey the tool I should be using is Ageis (I've seen that project a lot in the archives), but what I want to do is have a script called at the beginning of the commit process which takes the following action: No, you really do want to be using Aegis. http://www.canb.auug.org.au/~millerp/aegis.html Trying to do what you want to do with CVS is only going to end up being a bad hack. So my initial thought is why shouldn't the same user that has a global lock on the whole repository also be able to execute read-only operations like update or checkout that don't modify the repository's state? My guess is that it's simply easier to do lock management if locks aren't same-user-re-entrant and no other cvs operations are allowed once the commit starts. What does user identity have to do with repository integrity? The repoisitory is not likely in a consistent state when it's locked. It doesn't matter who locked it or who's trying to access it. -- 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
Newbie CVS commitinfo question
Hey everyone, I appologize in advance if this posted question appears twice on the list -- I initial posted it without joining (...my bad). I have a quick question about using the commitinfo admin file to perform a source-file check before commiting. Mabey the tool I should be using is Ageis (I've seen that project a lot in the archives), but what I want to do is have a script called at the beginning of the commit process which takes the following action: 1. Copy all submitted files from the /tmp/cvsprocess-number directory into a working directory on the CVS server associated with the user making the commit (the newly commited files would replace any files currently in that working directory). 2. Switch to that users working directory on the CVS server, and perform a cvs update -A -d to get the any previously submitted updates from the head of the repository. 3. Incrementally compile the whole project (this should result in only the currently submitted files and any modified files since the last commit being compiled). 4. Allow the commit to take place if the compile succeeds, or return a non-zero result and fail if the compile fails. This would be nice because it eliminates the problem of developers accidentally forgetting to add/ commit files which prevents other developers from being able to compile and test the project. It effectively guarantees that the head of the codebase will compile. The script to do this is straightforward -- and also doesn't work. It fails because trying to execute a cvs update -A -d command into another working directory on the server fails since the user trying to commit locks the entire repository (the command just hangs there with a message like ...trying to get lock from user-name). So my initial thought is why shouldn't the same user that has a global lock on the whole repository also be able to execute read-only operations like update or checkout that don't modify the repository's state? My guess is that it's simply easier to do lock management if locks aren't same-user-re-entrant and no other cvs operations are allowed once the commit starts. Anyways, if someone has a solution to this problem, I'll worship you like the software God/Godess you are! Also -- if for some reason I were to think about jumping into the code and making locks same-user-re-entrant during a commit, would anyone be interested in a source patch? Or is that a waste of time? ---Bryan _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: A not-so-CVS question
On Wed, Jul 10, 2002 at 08:31:44AM -0400, Lee Fellows wrote: On Wed, 2002-07-10 at 06:06, Isaac Claymore wrote: Hi, CVS folks. My question is not strictly related to CVS itself, but I think this list is the right place to ask. I've set up ViewCVS for my team, but then everyone on our LAN gets read access to the repository through it, which is not desired. So is there any tool or mechanism that's able to add authentication functionality to ViewCVS without hacking its code? Or, do you folks have similar experience? Thanks~~ -Clay If you are using apache as the web server, have you looked at .htaccess and .htpasswd? I've set up apache for authentication using various 'Auth*' tags. Thanks for your hints ;) ___ 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
A not-so-CVS question
Hi, CVS folks. My question is not strictly related to CVS itself, but I think this list is the right place to ask. I've set up ViewCVS for my team, but then everyone on our LAN gets read access to the repository through it, which is not desired. So is there any tool or mechanism that's able to add authentication functionality to ViewCVS without hacking its code? Or, do you folks have similar experience? Thanks~~ -Clay ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: A not-so-CVS question
On Wed, 2002-07-10 at 06:06, Isaac Claymore wrote: Hi, CVS folks. My question is not strictly related to CVS itself, but I think this list is the right place to ask. I've set up ViewCVS for my team, but then everyone on our LAN gets read access to the repository through it, which is not desired. So is there any tool or mechanism that's able to add authentication functionality to ViewCVS without hacking its code? Or, do you folks have similar experience? Thanks~~ -Clay If you are using apache as the web server, have you looked at .htaccess and .htpasswd? ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: java question?
I'm not sure, but you might be able to use the ClassLoader and reflection to achieve this although I suppose you'll want this info before run-time. OTOH, in order to build a set of classes used by the application (and not have any false negatives), using the ClassLoader will give you exactly that set. Im interested this but not sure how to go about it. can you give me a few pointers Id want to get the info on calling the main with a -version param From experience, if you do it the way you want, you'll have to contend with a lot of version-to-version dependency issues (eg which versions of class X will work with which versions of class Y?). It's much easier to deal with these issues from a larger-grained perspective (eg which versions of component/package/module X will work with which versions of component/package/module Y). the problem is that I have loads of classes in many different packages each applications individual classes are in a seperate package but they use many of the same util classes I often update my util classes, always keeping the same interfaces, but mabe adding others. If I update one of these I do not want to put a new 'tag' on the applications that use it for many reasons: 1: It wont change the application 2: I would have to look at every class in every application to see if it used the util class, and so then update it with a new tag or not 3: would not the util class have to have a different tag for each application that used it?(they might start stacking up) 4: all my applications are packaged in one jar and so will use the util class there not just the one when the application was last 'tagged' _ Send and receive Hotmail on your mobile device: http://mobile.msn.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: java question?
--- pootle monster [EMAIL PROTECTED] wrote: I'm not sure, but you might be able to use the ClassLoader and reflection to achieve this although I suppose you'll want this info before run-time. OTOH, in order to build a set of classes used by the application (and not have any false negatives), using the ClassLoader will give you exactly that set. Im interested this but not sure how to go about it. can you give me a few pointers Id want to get the info on calling the main with a -version param You'll have to find help elsewhere since I've never done it myself. From experience, if you do it the way you want, you'll have to contend with a lot of version-to-version dependency issues (eg which versions of class X will work with which versions of class Y?). It's much easier to deal with these issues from a larger-grained perspective (eg which versions of component/package/module X will work with which versions of component/package/module Y). the problem is that I have loads of classes in many different packages each applications individual classes are in a seperate package but they use many of the same util classes I often update my util classes, always keeping the same interfaces, but mabe adding others. If I update one of these I do not want to put a new 'tag' on the applications that use it for many reasons: I agree. You'll need to keep track of library version dependencies some other way. IOW, when it comes to using your utils jar file, treat them the way you would treat the JDK jar files. 1: It wont change the application I agree. 2: I would have to look at every class in every application to see if it used the util class, and so then update it with a new tag or not If you had a release cycle for the utils jar file, you will need to know which applications used it and test those for each new release of the utils jar file. Let's say you had several applications that worked with each other (thereby comprising a system). Would you then tag all the applications each time one of them was changed? I would think not, but rather, you would track version dependencies through some other means (possibly documentation). It's the same with library dependencies of applications. 3: would not the util class have to have a different tag for each application that used it?(they might start stacking up) Again, not if you track these kinds of dependencies from outside the version control tool. OTOH, I think some CMs use ClearCase in this way (versioning, not only third-party libraries, but tools (eg compilers) as well). This may be feasible to do in ClearCase. It is not in CVS. 4: all my applications are packaged in one jar and so will use the util class there not just the one when the application was last 'tagged' Again, this is a release issue, not a version control issue. Noel __ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Reverting question
On Wed, Jun 26, 2002 at 02:38:52PM +0100, Alex Zoro wrote: However, trying to perform the following command cvs admin -banim.c (i.e. we are trying to revert the file anim.c to the vendor version)causes the following error cvs [admin aborted]: usage is restricted to repository administrators In addition to what Larry said, your command is not quite right; it doesn't name the vendor branch. Use: cvs admin -bVENDOR_BRANCH anim.c where VENDOR_BRANCH stands for whatever name you gave your vendor branch when you did the initial import. -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / Anyone who swims with the current will reach the big music steamship; whoever swims against the current will perhaps reach the source. - Paul Schneider-Esleben ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: question about pserver
Schwenk, Jeanie writes: When on a remote unix host, the successfully logged in user always has to type cvs -d :pserver:generic@pilot:/usr/local/cvs co -c They can't just type cvs co -c? Logging in just associates a password with a CVSROOT specification, it doesn't set your current CVSROOT; you can be logged in to many different CVSROOTs at the same time (I'm currently logged in to 5 or 6). If you've set your $CVSROOT environment variable, you don't need to use -d on the command line (unless you want to override $CVSROOT). -Larry Jones It's either spectacular, unbelievable success, or crushing, hopeless defeat! There is no middle ground! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
question about pserver
I just want to verify what I've read because it seems wrong. When on a remote unix host, the successfully logged in user always has to type cvs -d :pserver:generic@pilot:/usr/local/cvs co -c They can't just type cvs co -c? Yes, I've read chapter 9. Jeanie __ This is Linux country. On a quiet night, you can hear NT re-boot. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: question about pserver
Correction ... that would be 2.9 -Original Message- From: Schwenk, Jeanie Sent: Friday, June 14, 2002 5:42 PM To: CVSpost (E-mail) Subject: question about pserver I just want to verify what I've read because it seems wrong. When on a remote unix host, the successfully logged in user always has to type cvs -d :pserver:generic@pilot:/usr/local/cvs co -c They can't just type cvs co -c? Yes, I've read chapter 9. Jeanie __ This is Linux country. On a quiet night, you can hear NT re-boot. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: shared working directories and advisory locks (Was: quick cvs question)
--- Paul Tomsic [EMAIL PROTECTED] wrote: Hi, Noel. Sorry to email you directly, but I was going thru the archive of the CVS mailing list and found an answer that you posted on 24.may.2002 regarding reserved locks Please send requests to [EMAIL PROTECTED] in the future. (Also, a more specific Subject: would be nice; I typically delete email with very general subjects). I think that we need to use reserved locks b/c we've got multiple developers using the same workspace b/c it's a web project. It doesnt' seem to make sense (to me) to have each developer use their own workspace, b/c to see their changes, they'd have to have a virt.web server pointing to their workspace, no? Am I way off the mark here? I'm new to the CVS implementation, so I'm open for suggestion. We're developing a web-app using JSPs/APACHE/Tomcat and beans. CVS is horrendous when sharing working directories. I think it has something to do with file ownership and possibly permissioning. One can view working directories as virtual branches. If one has a working directory per task, one can separate each change set from the others. So, my usual advice is to have one separate working directory for each task or change set (and thereby use a form of the Branch Per Task Pattern as described at http://www.enteract.com/~bradapp/acme/branching/patterns.html#BranchPerTask). Since you're using Apache/Tomcat, it shouldn't be too difficult for each developer to have their own web/app servers running and pointing to their own working directories. Going back to reserved locks, the patch has been renamed to the more appropriate advisory locks since: 1. It's up to the users to place advisory locks. 2. Users can override advisory locks. whereas, IMHO, reserved locks are forced by the server and cannot be overridden by the user. HTH, Noel __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: shared working directories and advisory locks (Was: quick cvs question)
thank you, and I appreciate your quick reply. Cheers, Paul --- Noel Yap [EMAIL PROTECTED] wrote: --- Paul Tomsic [EMAIL PROTECTED] wrote: Hi, Noel. Sorry to email you directly, but I was going thru the archive of the CVS mailing list and found an answer that you posted on 24.may.2002 regarding reserved locks Please send requests to [EMAIL PROTECTED] in the future. (Also, a more specific Subject: would be nice; I typically delete email with very general subjects). I think that we need to use reserved locks b/c we've got multiple developers using the same workspace b/c it's a web project. It doesnt' seem to make sense (to me) to have each developer use their own workspace, b/c to see their changes, they'd have to have a virt.web server pointing to their workspace, no? Am I way off the mark here? I'm new to the CVS implementation, so I'm open for suggestion. We're developing a web-app using JSPs/APACHE/Tomcat and beans. CVS is horrendous when sharing working directories. I think it has something to do with file ownership and possibly permissioning. One can view working directories as virtual branches. If one has a working directory per task, one can separate each change set from the others. So, my usual advice is to have one separate working directory for each task or change set (and thereby use a form of the Branch Per Task Pattern as described at http://www.enteract.com/~bradapp/acme/branching/patterns.html#BranchPerTask). Since you're using Apache/Tomcat, it shouldn't be too difficult for each developer to have their own web/app servers running and pointing to their own working directories. Going back to reserved locks, the patch has been renamed to the more appropriate advisory locks since: 1. It's up to the users to place advisory locks. 2. Users can override advisory locks. whereas, IMHO, reserved locks are forced by the server and cannot be overridden by the user. HTH, Noel __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Cvs migration question
Khalid Atitar writes: Can we use directly the repository created using v1.10.7 with the release V1.11.2 ? Yes, you can. All you need to do is replace your existing CVS executable with the new one. It's always a good idea to run cvs init after upgrading CVS to create any new administrative files, but it isn't strictly necessary. I'd suggest checking the NEWS file for any minor incompatibilities that may affect you: http://ccvs.cvshome.org/source/browse/ccvs/NEWS?rev=1.107content-type=text/x-cvsweb-markup -Larry Jones Can I take an ax to school tomorrow for ... um ... show and tell? -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Cvs migration question
Dear Mr. or Ms, My name is Khalid Atitar, the administrator in charge of Cvs. Actually, we are using the 1.10.7 version of Cvs and we would like to migrate to V1.11.2 without loosing the source files and preserving the recisions history. Can we use directly the repository created using v1.10.7 with the release V1.11.2 ? I would appreciate you telling me the way to perform this operation in the safest way. Kind regards, K.A.F ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
newbie cvs question for windows
I am using Windows 2000 to host cvs as a server. I am also using WinCVS as the client. Both are working and I can check things in and out. Currently, I set the server to run with the pserver protocol and the pserver impersonation. (1) I understand that pserver is a protocol that transmits the username/password/data in the clear, but what exactly is pserver impersonation? (2) I do not have ntserver or ntserver impersonation checked. If I read the information correctly (and it's very brief), ntserver protocol only works with NT/2000 client machines, so that if I use this protocol on the server, Linux/Unix machines won't be able to access the cvs server. Is this correct? I also was not clear on whether ntserver encrypts username/password/transmission of data. (3) When I use pserver, I need to type in a username and password. Just for fun, I switched pserver off, and turned on ntserver. On the command line of the server itself, I tried to login but could not (because that's for pserver), so I did a checkout without entering username/password. (a) How is it authenticating me? (b) If I wanted to use the command line from another machine to connect, what would be the syntax? That is, would I have to change the CVSROOT variable on the other machine, and if so, to what? (c) Assuming that the CVSROOT on the other machine does not contain a username/password, again, how is it authenticating me? Is it looking to see if I am a Windows user of the server machine? WINCVS: (1) In admin, preferences, what does the use version box represent? There are two options: standard or nt server. Is nt server mean that the cvs server is using the ntserver protocol? I wasn't sure because my cvs server was only using pserver and impersonation, and I was still able to do a log of a file while my wincvs client was set to using ntserver. What is the best way to encrypt username/password/data while using the cvs server on Windows and using WinCVS as a client? Sorry for all the questions. Thanks in advance. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
question about log command
I am new to CVS and am trying to get the log command to only output those files changed since a certain date or with a certain revision. When I use the -r or -d flag, the revision information is limited to the flag options, but I still get a header for every file (whether or not it has a relevant revision or change). Is there any way to display the file name and description, suppressing the header information? If not, does anyone have a good shell script to extract the just the file name and description info? Please reply by email as I am not subscribed to this list. Thank you Andy Kriger ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
CVS timestamping question
Hi: I am working with a bunch of people on a project and using a cvs repository. We are located all over the world and were wondering how cvs does timestamping to ensure we are always working with the latest version. Does it always use GMT? Is our timezone differences something we should be concerned about or do we not need to worry about it? We will all be using the the unix version of cvs. Thanks, Maneesh ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: question about log command
Andy Kriger writes: I am new to CVS and am trying to get the log command to only output those files changed since a certain date or with a certain revision. When I use the -r or -d flag, the revision information is limited to the flag options, but I still get a header for every file (whether or not it has a relevant revision or change). The most recent release of CVS (1.11.2) adds a -S option to suppress the header when no revisions are selected. -Larry Jones Even my FRIENDS don't do what I want. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS timestamping question
mshardogg writes: I am working with a bunch of people on a project and using a cvs repository. We are located all over the world and were wondering how cvs does timestamping to ensure we are always working with the latest version. Does it always use GMT? Is our timezone differences something we should be concerned about or do we not need to worry about it? We will all be using the the unix version of cvs. Yes, CVS uses UTC (aka GMT) internally so everything just works. -Larry Jones You can never really enjoy Sundays because in the back of your mind you know you have to go to school the next day. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS Question ?
Hi, you have to lock the branch - if you have one. A tag is not what you are looking for. Bye Oliver - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 16, 2002 4:38 PM Subject: CVS Question ? Is there a way to lock a tag so that no one can make any commits into that tag? After the release, we need to kind of freez that tag. Thanx, Sean ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
CVS Question ?
Is there a way to lock a tag so that no one can make any commits into that tag? After the release, we need to kind of freez that tag. Thanx, Sean
cvs history question?
Hello All: Can anyone help on cvs history command ? here is the question: I am forward the question from one of my engineer: what command I need to issue to try to determine what files have been changed on a branch since a particular date? I tried using cvs history with different flags and arg's but can't get it to do what I want, for example, I tried to put these things together cvs history -a -rBRANCH-IS41DEV -D2002-04-30 00:00 but it doesn't work -a: all users -rBRANCH-IS41DEV: the branch I am interested in -D2002-04-30 00:00: the starting date I'd like to see if any files have changed Thank you for your help in advances. Vinh Cao Unix systems admin [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
[help] cvs rm -f question
Dear all, I'm a newbie to cvs, please excuse me if my question is in FAQ. My problem is: - i have a local cvs server - after checking out a project, many changes has been made - because the changes include deleting files from the project, i must have used "cvs rm -f [filenames]" - unfortunately, instead of this command, i used "cvs rm -f" (without any file names!), and all files in the project directory are accidentally removed :-( Please help me recover deleted files, if it is possible. Thanks so much in advance, Nguyen Join Excite! - http://www.excite.comThe most personalized portal on the Web!
Re: [help] cvs rm -f question
Dear all, I'm a newbie to cvs, please excuse me if my question is in FAQ. My problem is: - i have a local cvs server - after checking out a project, many changes has been made - because the changes include deleting files from the project, i must have used cvs rm -f [filenames] I don't use cvs rm -f, for similar reasons. Destructive commands should be slightly awkward, and streamlining them is often a bad idea. - unfortunately, instead of this command, i used cvs rm -f (without any file names!), and all files in the project directory are accidentally removed :-( Please help me recover deleted files, if it is possible. Which files? If you didn't commit the changes, then you didn't change the repository. (If you did, it's possible to check out the files again and re-add them.) If you want to recover the files you deleted, it's probably impossible unless they were backed up. Unix has one-step file deletion, unlike the Macintosh and Microsoft Windows which have a two-step, and that two-step deletion has saved me on occasion. David H. Thornley| If you want my opinion, ask. [EMAIL PROTECTED] | If you don't, flee. http://www.thornley.net/~thornley/david/ | O- ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: [help] cvs rm -f question
Nguyen, In http://www.cvshome.org/docs/manual/cvs_7.html#SEC68 you will see: If you execute remove for a file, and then change your mind before you commit, you can undo the remove with an add command. $ ls CVS ja.h oj.c $ rm oj.c $ cvs remove oj.c cvs remove: scheduling oj.c for removal cvs remove: use 'cvs commit' to remove this file permanently $ cvs add oj.c U oj.c cvs add: oj.c, version 1.1.1.1, resurrected HOWEVER, the resurrected versions will not contain any local modifications that you had not checked in. If you had checked in your changes you are in luck. Dale Miller -Original Message- From: gmres [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 16, 2002 7:13 AM To: [EMAIL PROTECTED] Subject: [help] cvs rm -f question Dear all, I'm a newbie to cvs, please excuse me if my question is in FAQ. My problem is: - i have a local cvs server - after checking out a project, many changes has been made - because the changes include deleting files from the project, i must have used cvs rm -f [filenames] - unfortunately, instead of this command, i used cvs rm -f (without any file names!), and all files in the project directory are accidentally removed :-( Please help me recover deleted files, if it is possible. Thanks so much in advance, Nguyen Join Excite! - http://www.excite.com The most personalized portal on the Web! ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
CVS question
Hi: I can't seem to find out how to post a question via a web page. My question is this: When you commit a change to a CVS repository does CVS care about the time and date on the client machine? Or does it just time stame it with the servers time and date? The reason I ask is this, we are presently using Visual SS which gets very upset if the time and date is not synchronised with the server. I want to change over to a different source control system and CVS seems to do the job. However I cannot find out what commit does with the time and date. Paul Lundberg ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Question about CVS on Windows NT
Hi everybody, it's ok for my configuration of WinCVS ! The solution of Larry Jones was the good, it was effectly the / at the end of my CVSROOT in WINCVS which has caused me so much problems... I would like to thank you very much for the help you gave me, and especially Matt for the patience he had with me... Have a good day Nicolas. ** =?iso-8859-1?q?Nicolas=20PEZRON?= writes: so I have configured my inetd.conf file on the server, this is the line I have added to it : #CVS server cvspserver stream tcp nowait root /opt/cvs/bin/cvs cvs -f --allow-root=/cvs/CIDRE/CVSROOT pserver [...] so, I should be able to connect to the server with the user int because I have configured my CVSROOT on my WinCVS client like this : :pserver:int@cidre:/cvs/CIDRE/ The stuff after the last : (/cvs/CIDRE/) must *exactly* match an --allow-root option of the pserver, which it doesn't. I suspect they should both be /cvs/CIDRE (having a trailing slash can cause problems). -Larry Jones I'll be a hulking, surly teen-ager before you know it!! -- Calvin ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs checkout question
We switched to using CVS from PVCS a few months ago, and so far I like it a lot. However, there is one thing that I can't find any way to do, and would like to know if it is even possible. Can I just check out a single file, rather than the entire module? When I specify a filename with cvs checkout, it says cannot find module 'filename' - ignored. Sometimes I make changes to a file in my working copy and then decide they should be undone completely, or done in a different place (e.g., on the trunk rather than on my branch). In this case I want to overwrite my copy of that ONE file with a repository revision, but I don't want to check out the entire source tree. Is there any way to do this? In which case you have the files checked out, and want to update them in place. That's what cvs update is for. cvs checkout will create a CVS-controlled directory tree, and cvs update will maintain it after that. David H. Thornley| If you want my opinion, ask. [EMAIL PROTECTED] | If you don't, flee. http://www.thornley.net/~thornley/david/ | O- ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
cvs checkout question
We switched to using CVS from PVCS a few months ago, and so far I like it a lot. However, there is one thing that I can't find any way to do, and would like to know if it is even possible. Can I just check out a single file, rather than the entire module? When I specify a filename with cvs checkout, it says cannot find module 'filename' - ignored. Sometimes I make changes to a file in my working copy and then decide they should be undone completely, or done in a different place (e.g., on the trunk rather than on my branch). In this case I want to overwrite my copy of that ONE file with a repository revision, but I don't want to check out the entire source tree. Is there any way to do this? BTW, we are using CVS version 1.11.1p1. Thanks very much. -Ariel Canright ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs checkout question
[EMAIL PROTECTED] writes: to know if it is even possible. Can I just check out a single file, rather than the entire module? When I specify a filename with cvs checkout, it says cannot find module 'filename' - ignored. Then you're not specifying the filename correctly -- you have to specify both the module and the file name. For example, if you have a module called foo that contains the files foo1 and foo2. If you do: cvs checkout foo you'll get a directory foo and the files foo/foo1 and foo/foo2. If you just want to checkout the file foo1, you do: cvs checkout foo/foo1 Sometimes I make changes to a file in my working copy and then decide they should be undone completely, or done in a different place (e.g., on the trunk rather than on my branch). In this case I want to overwrite my copy of that ONE file with a repository revision, but I don't want to check out the entire source tree. Is there any way to do this? cvs update -C file -Larry Jones I take it there's no qualifying exam to be a Dad. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Question about CVS on Windows NT
Nicolas PEZRON wrote: finally, I have decided to use WinCVS as a client and a server Unix as a CVS server when I try to connet to the CVS server, I have the following error : cvs login: authorization failed: server cidre rejected access to /cvs/CIDRE/ for user int I don't know how to configure the passwords there is a menu in Admin which is WinCVW and there is a place to put the folder for the passwords I don't know what to put here You need to configure passwords on the server, not the client. See the manual for details: http://www.cvshome.org/docs/manual/cvs_2.html#SEC29 -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Question about CVS on Windows NT
Nicolas PEZRON wrote: so I have configured my inetd.conf file on the server, this is the line I have added to it : #CVS server cvspserver stream tcp nowait root /opt/cvs/bin/cvs cvs -f --allow-root=/cvs/CIDRE/CVSROOT pserver Make sure you have an entry in /etc/services like: cvspserver 2401/tcp I have also created a passwd file in my $CVSROOT/CVSROOT folder, this is my passwd file : int: This looks ok. so, I should be able to connect to the server with the user int because I have configured my CVSROOT on my WinCVS client like this : :pserver:int@cidre:/cvs/CIDRE/ The entry in inetd.conf says that your repository path is /cvs/CIDRE/CVSROOT, while your $CVSROOT is set to /cvs/CIDRE/; they have to be the same. I'm guessing you want to remove the extra CVSROOT from your inetd.conf. Good luck. -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Question about CVS on Windows NT
Hi, finally, I have decided to use WinCVS as a client and a server Unix as a CVS server when I try to connet to the CVS server, I have the following error : cvs login: authorization failed: server cidre rejected access to /cvs/CIDRE/ for user int I don't know how to configure the passwords there is a menu in Admin which is WinCVW and there is a place to put the folder for the passwords I don't know what to put here thank you very much for you answer Nicolas. --- Matt Riechers [EMAIL PROTECTED] a écrit : Nicolas PEZRON wrote: may I stock Windows files in my CVS tree on Unix or do I have to use a version of CVS for Windows ? (I tried to see for WinCVS but if I can use CVS on Unix, it will be better for me) If it is easy for you to get at files on the UNIX box from Windows, then you don't necessarily need WinCVS. In that case, you should make sure that your Windows editor doesn't change the file line endings to DOS format. If that's a big problem, you might be better off with using WinCVS. I have also heart about cvs on windows but with a unix cvs server, how does it work ? http://www.cvshome.org/docs/manual/cvs_2.html#SEC26 -Matt ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Question about CVS on Windows NT
when I try to connet to the CVS server, I have the following error : cvs login: authorization failed: server cidre rejected access to /cvs/CIDRE/ for user int You need to configure passwords on the server, not the client. See the manual for details: http://www.cvshome.org/docs/manual/cvs_2.html#SEC29 ok so I have configured my inetd.conf file on the server, this is the line I have added to it : #CVS server cvspserver stream tcp nowait root /opt/cvs/bin/cvs cvs -f --allow-root=/cvs/CIDRE/CVSROOT pserver I have also created a passwd file in my $CVSROOT/CVSROOT folder, this is my passwd file : int: so, I should be able to connect to the server with the user int because I have configured my CVSROOT on my WinCVS client like this : :pserver:int@cidre:/cvs/CIDRE/ but I have always the following message : cvs login: authorization failed: server cidre rejected access to /cvs/CIDRE/ for user int could you help me please, I begin to discourage myself thank you very much and thank you for your previous answers Nicolas. ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Question about CVS on Windows NT
=?iso-8859-1?q?Nicolas=20PEZRON?= writes: so I have configured my inetd.conf file on the server, this is the line I have added to it : #CVS server cvspserver stream tcp nowait root /opt/cvs/bin/cvs cvs -f --allow-root=/cvs/CIDRE/CVSROOT pserver [...] so, I should be able to connect to the server with the user int because I have configured my CVSROOT on my WinCVS client like this : :pserver:int@cidre:/cvs/CIDRE/ The stuff after the last : (/cvs/CIDRE/) must *exactly* match an --allow-root option of the pserver, which it doesn't. I suspect they should both be /cvs/CIDRE (having a trailing slash can cause problems). -Larry Jones I'll be a hulking, surly teen-ager before you know it!! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Question about CVS on Windows NT
Nicolas PEZRON wrote: may I stock Windows files in my CVS tree on Unix or do I have to use a version of CVS for Windows ? (I tried to see for WinCVS but if I can use CVS on Unix, it will be better for me) If it is easy for you to get at files on the UNIX box from Windows, then you don't necessarily need WinCVS. In that case, you should make sure that your Windows editor doesn't change the file line endings to DOS format. If that's a big problem, you might be better off with using WinCVS. I have also heart about cvs on windows but with a unix cvs server, how does it work ? http://www.cvshome.org/docs/manual/cvs_2.html#SEC26 -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Question about CVS on Windows NT
Hello everybody, I am a french student and I have to work on CVS during my internship... I have 2 kinds of files : some Unix files on a Unix server and some Windows files on Windows NT server... I have yet installed a CVS tree for Unix and it is ok but I have a problem for my Unix files... may I stock Windows files in my CVS tree on Unix or do I have to use a version of CVS for Windows ? (I tried to see for WinCVS but if I can use CVS on Unix, it will be better for me) what are the constraints in that case ? I have also heart about cvs on windows but with a unix cvs server, how does it work ? thank you very much for your answer Nicolas Pezron. ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
cvs prune question
Hi, When updating a module using the command 'cvs update', CVS prints lines which look something like this. M project/src/com/company/Test1.java M project/src/com/company/Test2.java P project/src/com/company/Test3.java I know the M means merge, and I suspect the P means prune. Can someone confirm that for me? If that's true, why is it performing this action without the -P switch, and what does it mean in this context? Thanks for your help, Dave ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs prune question
Daniels, Dave F writes: I know the M means merge, and I suspect the P means prune. No, it means patch. See the manual: http://www.cvshome.org/docs/manual/cvs_16.html#SEC152 -Larry Jones Something COULD happen today. And if anything DOES, by golly, I'm going to be ready for it! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS question
In [EMAIL PROTECTED] =?iso-8859-1?q?Nicolas=20PEZRON?= [EMAIL PROTECTED] writes: I thought that to you use CVS, you had to copy the source of your first version of your program and after, you will be able to retrieve all the versions of your program More or less. You clean up your source tree of compiled objects and other generated files and you import it into CVS. You can then delete the sources (!) but most people get a bit nervous at this point and prefer to tar or zip the tree into an archive before blowing it away. You then check out a new copy (sandbox) from CVS and work on it forevermore, never going close to the original source tree or its archive. but, if you want to add a new file to your CVS tree, do you have to copy first the source of this file in order to be able to retrieve its versions after ? Copy it from where? Normally you will have created the new file right in the sandbox, since that's where you normally work. You do need to tell CVS about the new file with the 'cvs add' command, but that's about it. The next time you commit, the first revision of your new file will be created in the repository. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
CVS question
Hello, I am a french student and I have to work on CVS during my internship I have a question : I thought that to you use CVS, you had to copy the source of your first version of your program and after, you will be able to retrieve all the versions of your program but, if you want to add a new file to your CVS tree, do you have to copy first the source of this file in order to be able to retrieve its versions after ? or is it not necessary ? thanks a lot for your answer Nicolas Pezron. ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Ampersand module question
In PkXs8.421$[EMAIL PROTECTED] Jay Glanville [EMAIL PROTECTED] writes: Thanks Martin. It's a good start, but not all that I was looking for. By using the -d option, what I'm doing is front-loading the naming architecture. In other words, anytime I use module amp1, it will be under a directory tools I create dummy modules for that purpose. For example, amp1path/to/amp1 amp2path/to/amp2 _amp1 -d tools/amp1 path/to/amp1 mod path/to/mod _amp1 amp2 The convention is that a module beginning with an underscore is not meant to be checked out by itself --although nothing prevents you to. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Ampersand module question
Pierre Asselin [EMAIL PROTECTED] wrote in message a92viq$oed$[EMAIL PROTECTED]">news:a92viq$oed$[EMAIL PROTECTED]... In PkXs8.421$[EMAIL PROTECTED] Jay Glanville [EMAIL PROTECTED] writes: Thanks Martin. It's a good start, but not all that I was looking for. By using the -d option, what I'm doing is front-loading the naming architecture. In other words, anytime I use module amp1, it will be under a directory tools I create dummy modules for that purpose. For example, amp1path/to/amp1 amp2path/to/amp2 _amp1 -d tools/amp1 path/to/amp1 mod path/to/mod _amp1 amp2 The convention is that a module beginning with an underscore is not meant to be checked out by itself --although nothing prevents you to. Thanks Pierre. This makes sense. JDG ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Ampersand module question
In [EMAIL PROTECTED] Martin Heinen [EMAIL PROTECTED] writes: On Tue, Apr 09, 2002 at 01:09:27PM +, Jay Glanville wrote: [ ... ] Now, is there a way to say that module amp1 should be included in module mod and be placed in a directory called tools. For example, when I do a checkout of module mod, I get the following directories: mod mod/tools/amp1 mod/amp2 The -d option renames the working directory: | amp1 -d mod/tools/amp1 amp1 | amp2 amp2 | mod amp1 amp2 I think it should be '-d tools/amp1', the 'mod/' is implied by the amperstand mechanism. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Ampersand module question
Martin Heinen [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... On Tue, Apr 09, 2002 at 01:09:27PM +, Jay Glanville wrote: When a module has an ampersand module as part of it's definition, the ampersand module gets included in the root of the other module. My questio is: is there a way to have the ampersand module included in a subdirectory? For example, if my modules file looks something like this: amp1 amp1 amp2 amp2 mod amp1 amp2 then when I do a: cvs co mod I get a directory structure that looks like this: mod mod/amp1 mod/amp2 Now, is there a way to say that module amp1 should be included in module mod and be placed in a directory called tools. For example, when I do a checkout of module mod, I get the following directories: mod mod/tools/amp1 mod/amp2 The -d option renames the working directory: | amp1 -d mod/tools/amp1 amp1 | amp2 amp2 | mod amp1 amp2 Module options are described in http://www.cvshome.org/docs/manual/cvs_18.html#SEC160 HTH, Martin Thanks Martin. It's a good start, but not all that I was looking for. By using the -d option, what I'm doing is front-loading the naming architecture. In other words, anytime I use module amp1, it will be under a directory tools (i.e.: cvs co amp1 will result in tools/amp1). Another example: along with module mod is module othermod, which has a definition of othermod amp1. It will automaticly be placed in a directory called othermod/tools/amp1. I may not want it there. Is there a way to back-load where the ampersand module will be included? For example, to be able to say that in module mod, include module amp1 in the location mod/tools, and for module othermod, include module amp1 in location othermod/loadbuild? I suppose another word to describe what I'm trying to do is make a link to another module. In ClearCase parlance, I'd be making a link (at a location of my choosing) to another vob (equivalent to a module). Thanks JDG -- Jay Dickon Glanville ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Ampersand module question
I have a question concerning ampersand modules, and I'm hoping someone here can help me. When a module has an ampersand module as part of it's definition, the ampersand module gets included in the root of the other module. My questio is: is there a way to have the ampersand module included in a subdirectory? For example, if my modules file looks something like this: amp1 amp1 amp2 amp2 mod amp1 amp2 then when I do a: cvs co mod I get a directory structure that looks like this: mod mod/amp1 mod/amp2 Now, is there a way to say that module amp1 should be included in module mod and be placed in a directory called tools. For example, when I do a checkout of module mod, I get the following directories: mod mod/tools/amp1 mod/amp2 Is this possible? Thanks, JDG -- Jay Dickon Glanville ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Ampersand module question
On Tue, Apr 09, 2002 at 01:09:27PM +, Jay Glanville wrote: When a module has an ampersand module as part of it's definition, the ampersand module gets included in the root of the other module. My questio is: is there a way to have the ampersand module included in a subdirectory? For example, if my modules file looks something like this: amp1 amp1 amp2 amp2 mod amp1 amp2 then when I do a: cvs co mod I get a directory structure that looks like this: mod mod/amp1 mod/amp2 Now, is there a way to say that module amp1 should be included in module mod and be placed in a directory called tools. For example, when I do a checkout of module mod, I get the following directories: mod mod/tools/amp1 mod/amp2 The -d option renames the working directory: | amp1 -d mod/tools/amp1 amp1 | amp2 amp2 | mod amp1 amp2 Module options are described in http://www.cvshome.org/docs/manual/cvs_18.html#SEC160 HTH, Martin -- Marxpitn ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
wincvs - read only question
Hi, how can i switch a file from read-only access to writable using wincvs. Thanks Andy Brown ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
WinCvs question
Hi there. I hope I am sending this to the correct address.. I have downloaded the 'stable' version of WinCvs (1.2) and I'm trying to get it to work. I have managed to get it to start but I need some guidance on what I need to do to run in NT mode, to call it that. The server I am installing it on does not and will not have either linux or unix installed so I need to bypass all the linux/unix issues like password authentification and so on. Added to this, can you please give me some info on the client/server setup and what I would need to do to enable others (who I would assume to use client software) to log onto the server. I am not a systems administrator hence this isn't my type of work but it's something I was asked to do and I am keen to learn more in this regard. Thanks in advance Regards Quentin Smit American Management Systems The Netherlands [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Question on multiple repositories
On Thu, 4 Apr 2002, Max wrote: Date: Thu, 04 Apr 2002 01:23:18 GMT From: Max [EMAIL PROTECTED] To: [EMAIL PROTECTED] Newsgroups: gnu.cvs.help Subject: [info-cvs] Question on multiple repositories I'm brand new at the CVS game and have no senior resource available at work, so I'm hoping that I can get some help here. The specs I was handed at the office call for an open development repository and a secure QA/production repository. This is nonsense; everyone can work from the same repository. Once developers finish their stuff, a baseline is made and the code is replicated to the QA repository. This is the step where I'm having a problem. CVS can assign a symbolic revision to the baseline. This is done using cvs rtag. A branch can be made from the symbolic revision when critical bugs need to be fixed in a build that is identified as a release candidate. So no separate repository is needed to stabilize code. If you really want a stable second level repository, simply use CVS's import feature to import snapshots on the vendor branch. That is, treat the devoper team as a third-party source code ``vendor''. which at this time is empty. I set my CVSROOT to point the development, check out based on a tag, then try get the code into the QA repository. First I set my CVSROOT to point to the QA repository, then use commit to move the code. Alternatively, since there are no modules in the QA repository, I try to use add. Both fail because I still appear to be pointing to the development repository. I'm hesitant to use import because (as I understand it) this command will club the previous versions under the same name (down the road). No, import does not club anything, it adds new versions. So the question I have is how do I move source from one repository to the other? Is there a way to save the baseline and the version numbers in the process. Not without copying the RCS files themselves, which simply gives you an exact replica of the repository, not a different repository that contains only the stable baselines you want. -- Meta-CVS: solid version control tool with directory structure versioning. http://users.footprints.net/~kaz/mcvs.html ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Question on multiple repositories
I'm brand new at the CVS game and have no senior resource available at work, so I'm hoping that I can get some help here. The specs I was handed at the office call for an open development repository and a secure QA/production repository. Once developers finish their stuff, a baseline is made and the code is replicated to the QA repository. This is the step where I'm having a problem. I have the development repository up and running and made a QA repository, which at this time is empty. I set my CVSROOT to point the development, check out based on a tag, then try get the code into the QA repository. First I set my CVSROOT to point to the QA repository, then use commit to move the code. Alternatively, since there are no modules in the QA repository, I try to use add. Both fail because I still appear to be pointing to the development repository. I'm hesitant to use import because (as I understand it) this command will club the previous versions under the same name (down the road). So the question I have is how do I move source from one repository to the other? Is there a way to save the baseline and the version numbers in the process. Any help would be greatly appreciated. Max ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Question on multiple repositories
Hi Max, CVS stores metadata about the current repository in the sandbox; notice that there are subdirs named CVS/ in every CVS-controlled directory. You can't just change your CVSROOT, since revision numbers and other important metadata will be incorrect, since the state of your sandbox is stored on the client side. You either need - 1) two seperate checkouts, and copy the files between these two checkouts. 2) branches ( see http://www.cvshome.org/docs/manual/cvs_5.html#SEC54 ) I recommend branches. Either way should work fine, but there's really no good reason to have seperate repositories, it's alot more work that you have to do ( which means more potential for human error :P ). HTH, Rob On Thu, Apr 04, 2002 at 01:23:18AM +, Max wrote: I'm brand new at the CVS game and have no senior resource available at work, so I'm hoping that I can get some help here. The specs I was handed at the office call for an open development repository and a secure QA/production repository. Once developers finish their stuff, a baseline is made and the code is replicated to the QA repository. This is the step where I'm having a problem. I have the development repository up and running and made a QA repository, which at this time is empty. I set my CVSROOT to point the development, check out based on a tag, then try get the code into the QA repository. First I set my CVSROOT to point to the QA repository, then use commit to move the code. Alternatively, since there are no modules in the QA repository, I try to use add. Both fail because I still appear to be pointing to the development repository. I'm hesitant to use import because (as I understand it) this command will club the previous versions under the same name (down the road). So the question I have is how do I move source from one repository to the other? Is there a way to save the baseline and the version numbers in the process. Any help would be greatly appreciated. Max ___ 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: Question on multiple repositories
In aWNq8.14247$[EMAIL PROTECTED] Max [EMAIL PROTECTED] writes: I'm brand new at the CVS game and have no senior resource available at work, so I'm hoping that I can get some help here. The specs I was handed at the office call for an open development repository and a secure QA/production repository. Once developers finish their stuff, a baseline is made and the code is replicated to the QA repository. This is the step where I'm having a problem. Complicated. Call it a formal release from dev to QA: cvs export from dev, cvs import in QA. At the same time, dev creates a bugfix branch and checks out a sandbox on it. When QA fixes a bug, it sends a patch to dev, who applies it to the bugfix sandbox, commits, and merges back to the trunk. I'm hesitant to use import because (as I understand it) this command will club the previous versions under the same name (down the road). That's what you have to do, though. The QA people will just have to learn how to do pre-import tags and post-import merges. It's a lot more trouble for them too, but those are the consequences of the rules imposed on you. Note that an import doesn't destroy previous imports. It can break the trunk until the post-import merge is finished, but past imports are always available through their tags. Faint glimmer of hope: what do they mean by secure QA? If secure really means secure, you're in the import/export business and that's that. If secure only means commits to QA tress are restricted, then you *might* get away with commitinfo scripts that reject commits by developers when on a QA branch. Understand that this is not secure at all, in that a developer determined to break company rules can probably defeat the system. It will only prevent casual or inadvertent commits. If acceptable, this would be *much* better for all: a single repository, dev releases to QA simply by creating a tag, QA creates and manages the bugfix branch, dev merges directly from the branch to the trunk. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
