Re: -chroot patch for CVS ?
The author of rsync has a 'pserver' wrapper program which chroots before running cvs pserver. It's used for the samba and rsync anonymous cvs access. See the note about 'how it's done' on this page: http://www.samba.org/samba/cvs.html It directs you to check out the code itself from cvs: cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot co pserver I've examined it a while back but have not put it into practice. Brilliant, thanks! (unfortunately, http://www.samba.org is currently not very responsive, though, so I'll have to wait before trying). Incidentally, in case it interests people (or posterity browsing groups.google.com :-), I also found another patches/projects that would appear to be relevant to securing public CVS access: idx-chrooted-ssh (http://www.idealx.org/prj/idx-chrooted-ssh-cvs/index.en.html) cvs-nserver (http://alexm.here.ru/cvs-nserver/) Enjoy, Philip -- The mail transport agent is not liable for any coffee stains in this message - Philip Lijnzaad, [EMAIL PROTECTED] European Bioinformatics Institute,rm A2-08 +44 (0)1223 49 4639 Wellcome Trust Genome Campus, Hinxton +44 (0)1223 49 4468 (fax) Cambridgeshire CB10 1SD, GREAT BRITAIN ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Kids Writing PUBLISHED....
I am looking for the new website that publishes unknown child authors. My kids heard about it at school and they desperately want to enter the writing contests. Has anyone heard of it? How can I get more info? ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
stopping 'cvs tag -b'
Since I didn't see any responses, I thought I would ask this once more: How can I keep users from doing 'cvs tag -b' and still allow 'cvs tag' I'm aware of CVSROOT/taginfo, but I don't see any arguments that indicate whether it will create a branch or not. $2 only has 'add', 'mov', 'del'. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
verifymsg script problem
I've tried to use the sample script that can be found in the manual, and
like I was advised by Jerry (thanks!) I did as followed:
1) Checked out CVSROOT
cvs co CVSROOT
2) added a directory for the script and template
cd CVSROOT
mkdir cvsscripts
cvs add cvsscripts
3) added my script and template
cd cvsscripts
cp ...somewhere.../bugid.verify ...somewhere.../bugid.template .
cvs add bugid.*
cvs ci -m new bugid stuff bugid.*
cd ..
4) added these files to the checkoutlist
echo cvsscripts/bugid.verify checkoutlist
echo cvsscripts/bugid.template checkoutlist
cvs ci -m new bugid stuff checkoutlist
5) added the required lines to verifymsg and rcsinfo
echo '^Test $(CVSROOT)/CVSROOT/cvsscripts/bugid.verify' verifymsg
echo '^Test $(CVSROOT)/CVSROOT/cvsscripts/bugid.template' rcsinfo
cvs ci -m new bugid stuff verifymsg rcsinfo
My script file (bugid.verify) was copied from the manual, and looked like
this:
#!/bin/sh
#
# bugid.verify filename
#
# Call $EDITOR on FILENAME, and verify that the
# resulting file contains a valid bugid on the first
# line.
if [ x$EDITOR = x ]; then EDITOR=vi; fi
if [ x$CVSEDITOR = x ]; then CVSEDITOR=$EDITOR; fi
$CVSEDITOR $1
until head -1|grep '^BugId:[ ]*[0-9][0-9]*$' $1
do echo -n No BugId found. Edit again? ([y]/n)
read ans
case ${ans} in
n*) exit 1;;
esac
$CVSEDITOR $1
done
and when I used it it gave me the following error:
cvs commit: cannot exec /home/cvsroot/CVSROOT/cvsscripts/bugid.verify: No
such file or directory
cvs [commit aborted]: Message verification failed
I removed the comment lines from the beginning and used this script:
if [ x$EDITOR = x ]; then EDITOR=emacs; fi
if [ x$CVSEDITOR = x ]; then CVSEDITOR=$EDITOR; fi
$CVSEDITOR $1
until head -1|grep '^BugId:[ ]*[0-9][0-9]*$' $1
do echo -n No BugId found. Edit again? ([y]/n)
read ans
case ${ans} in
n*) exit 1;;
esac
$CVSEDITOR $1
done
and now I'm getting this error:
'home/cvsroot/CVSROOT/cvsscripts/commentcheck.edit: line 7: syntax error
near unexpected token `in
'home/cvsroot/CVSROOT/cvsscripts/commentcheck.edit: line 7: `case ${ans}
in
cvs [commit aborted]: Message verification failed
Does anyone can help me with that? I'm really stuck here.
Thanks,
Roni.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
list of editors in notify
I have CVS setup to map CVS users to a single system user. I'd like to be able to use the notify feature to send the editors of files updates on their change of status (via email or Winpopups). Using %s and $CVSROOT/CVSROOT/users won't work, because the CVS users map to the system user. Is the list of editors available to the script as a CVS variable (like $USER)? Otherwise, it appears the only way would be to parse .../CVS/fileattr from the script run from notify, grabbing the file path from the notify message. Any suggestions? Thanks, -- Michael Santos [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
CVS and Delphi
Is anyone using CVS to store Borland Delphi source code, as I am unsure how to link our versions of components with versions of source code ? Andrew Oates Tel: +44 (0) 1959 579000 Fax: +44 (0) 1959 579039 __ This electronic mail message and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, please notify us on +44 (0) 1959 579000 immediately: you should not copy it or use it for any purpose, nor disclose its contents to any person. This electronic mail message and attachments have been swept for known computer viruses. Formula One Management Ltd Postmaster [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cannot open file Utils.pm for comparing: No such file or directory
Philip Lijnzaad [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... Dear all, I have a strange problem: I can cvs update and commit and everything without a problem, but when doing a cvs diff, I get: cvs [server aborted]: cannot open file Utils.pm for comparing: No such file or directory The CVSROOT is ':ext:[EMAIL PROTECTED]:/ebi/cvs' and my CVS_RSH is ssh. What can cause this kind of behavior ? It looks a bit like the repository side can't create a temporary file to 'diff' against. Turns out that I had ''diff -kk'' in my ~/.cvsrc. Out-commenting this made the problem go away. Incidentally, this problem only occured on Solaris and TrueUnix, not SGI and Linux. The version I used it with was 1.10 halibut. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS a Web site
On Wed, Oct 17, 2001 at 04:22:28PM -0400, Jason Purdy wrote: What is a good scheme of automating synchronization between a CVS repository and a Web site... A few links about the way(s) that others have used CVS with web sites: http://www.durak.org/cvswebsites/howto-cvs/ http://philip.greenspun.com/wtr/cvs.html I'm sure there are others. Google is your friend. Steve ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS - setup reserved checkout
How does one use the reserved locks? Jerzy Kaczorowski wrote: - Original Message - From: Paul Sander [EMAIL PROTECTED] There's Noel Yap's patches on SourceForge, which apply to a down-rev release of CVS. I believe that others have implemented it as well, but only privately in their own shops. Maybe they don't advertise them for fear of being blasted by Greg. Noel Yap's patches have been succesfully applied into the cvsnt (www.cvsnt.org) long time ago and prove to work and be usefull. Jerzy ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Reserved locks
Though I had to tell patch where each file was by hand and I had to go back 2 versions on cvs, I think I know have Yap's reserved locks. But how does one use them? ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS a Web site
Jason Purdy [EMAIL PROTECTED] writes: Hi, What is a good scheme of automating synchronization between a CVS repository and a Web site (or does a repository have to be separated from the Web site files [besides renaming the files from the ,v suffix])? A co-worker I The repository *must* be separate from the website and developer directories. PS: Here are some of my ideas: 1) Create a Perl script/Cron job (run every 15 minutes) which would basically 'cvs history -a -c -D 15 minutes ago', parse that and affect the Web site directories accordingly. 2) Create 'trigger' scripts which would be triggered when the developer 'commit'ed their changes, which would also affect the changes on the Web site directories. Here are my ideas, which I stole from smart people :-) like Nik Clayton and Phillip Greenspun. Use Makefiles and the make utility to implement the triggering: make checkout to checkout a site into a new working directory make update to commit/update changes in a working directory make test to put the latest version in the test site, if you have one make production to put the latest version in the live production site pserver commands allow for the repository, development, test and host servers to be different, which is usually a good practice. Chris ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
rcsinfo question
I am attempting to use rcsinfo to display a small custom commit log template. I have a test project in cvs I am working on so the rcsinfo file looks like this: test_project /home/cvsuser/repo/CVSROOT/checkintemplate I then attempt a commit to "test_project". Despite the fact that /home/cvsuser/repo/CVSROOT/checkintemplate exists on the server, the client continues to display the default template in the editor of your choice.. (in my case, vi)... I have not found any info on the net or in manuals that refer to problems with this or steps I might have to take to get it to work. Am I missing something here? Does anyone have any idea?? thanks in advance!!! markl
Re: CVS export
[ On Wednesday, October 17, 2001 at 15:25:51 (GMT), Tom Sanidas wrote: ] Subject: CVS export Do I have to go through my modules and create a fake tag for each of them before I export, or should I just use checkout? Any suggestions? Depending on what you use your nightly builds for, it may be best to tag them for cvs export. You might simply move the tag every night, or you might keep a circular queue of several such tags. Of course that begs the question of who's going to do the tag and based on what criteria. On the other hand if you don't use the products of the builds for any testing that could last beyond the next build then a tag and cvs export might be over-kill -- just use a normal checkout of the head of whatever branch you're building. If you simply want to be pedantic about testing a moving release baseline (which your process may require be done with cvs export) then you could simply keep a nightly tag at the head of your working branch like this: cvs -q rtag -F -f NIGHTLY-BUILD mymodule cd /buildtmp cvs export -r NIGHTLY-BUILD -d mymodule-$(date '+%Y%m%d) -kv mymodule cd mymodule-$(date '+%Y%m%d) make check -- Greg A. Woods +1 416 218-0098 VE3TCP [EMAIL PROTECTED] [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Why can't root check in files?
[ On Thursday, October 18, 2001 at 13:01:11 (+1000), [EMAIL PROTECTED] wrote: ] Subject: Re: Why can't root check in files? Most of the text files in /etc are used as-is, which is why I think it's okay to use CVS in an unusual way in this case. Just because a file is used as-is -- i.e. doesn't require any transformation or translation, is not any reason to ignore all the process related reasons why you _need_ a build system -- Greg A. Woods +1 416 218-0098 VE3TCP [EMAIL PROTECTED] [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS export
[ On Wednesday, October 17, 2001 at 11:40:38 (-0700), John Minnihan wrote: ] Subject: Re: CVS export Why use export? For all the same reasons you should use cvs export when checking out any actual release. -- Greg A. Woods +1 416 218-0098 VE3TCP [EMAIL PROTECTED] [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Kids Writing PUBLISHED....
I think I found the website you mean, my kids are going nuts about the writing contest. You can get the rules for the contest and a FREE SAMPLE by sending a blank email to: [EMAIL PROTECTED] They are going to have more contests, the prize is getting published (and they pay)! The company is just starting out, they are desperate for entries!!! The website is www.galaxymall.com/children/writingclubhouse I hope I helped you out. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Why can't root check in files?
In article [EMAIL PROTECTED], Greg A. Woods wrote: [ On Thursday, October 18, 2001 at 13:01:11 (+1000), [EMAIL PROTECTED] wrote: ] Subject: Re: Why can't root check in files? Most of the text files in /etc are used as-is, which is why I think it's okay to use CVS in an unusual way in this case. Just because a file is used as-is -- i.e. doesn't require any transformation or translation, is not any reason to ignore all the process related reasons why you _need_ a build system Also I disagree about the ``as is'' to begin with. The file metadata such as permissions will not be properly versioned if the sandbox is made to serve as the deployment directory. Basically, the sandbox file will inherit its permissions from the corresponding ,v file in the repository. Changing the permissions on a ,v will affect all versions simultaneously, so the idea of recoverable configuration---which is the central concept in version control---goes out the window. You will get better version control if you just edit your /etc directory in place and do daily backups of it instead of fussing about with CVS. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS - setup reserved checkout
I sent out instructions within the several threads about this. I guess you missed it 'cos you were too busy ranting. Please check the archives. Noel How does one use the reserved locks? Jerzy Kaczorowski wrote: - Original Message - From: Paul Sander [EMAIL PROTECTED] There's Noel Yap's patches on SourceForge, which apply to a down-rev release of CVS. I believe that others have implemented it as well, but only privately in their own shops. Maybe they don't advertise them for fear of being blasted by Greg. Noel Yap's patches have been succesfully applied into the cvsnt (www.cvsnt.org) long time ago and prove to work and be usefull. Jerzy ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase Co., its subsidiaries and affiliates. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS export
[EMAIL PROTECTED] wrote: [ On Wednesday, October 17, 2001 at 11:40:38 (-0700), John Minnihan wrote: ] Subject: Re: CVS export Why use export? For all the same reasons you should use cvs export when checking out any actual release. building =//= releasing, especially when the build is already understood to be an 'overnite' which is at the very bottom of the food chain. Use of 'cvs export' to collect sources that are used to produce a build is almost never necessary. This implies that the sources themselves are part of the resulting build (and thus should be cleansed of the CVS structure) and this generally is not true. If unmodifed sources or file structures collected directly from CVS constitute all or part of your 'build', then 'cvs export' may be useful. -- John Minnihan mailto:[EMAIL PROTECTED] http://www.freepository.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS export
Tom == Tom Sanidas [EMAIL PROTECTED] writes:
Tom Hi, I'm trying to use cvs export to do a nightly build sort
Tom of thing. I'm trying to get the current versions of the main
Tom trunk exported to a set of directories that I'll use to
Tom perform a build. I've tried using -D and today's date,
Tom but cvs misses some files that way.
I usually say -D now. I know -D today would work, too, but I'm
not sure if it means midnight (00:00) of today. So, I say now.
Are the missing files present on the branch you're trying to export?
CVS won't export files not in the branch being exported, AFAIK.
Tom Do I have to go through
Tom my modules and create a fake tag for each of them before I
Tom export, or should I just use checkout? Any suggestions?
I don't think so.
--
Lee Sau Dan §õ¦u´°(Big5)~{@nJX6X~}(HZ)
..
| e-mail: [EMAIL PROTECTED]http://www.csis.hku.hk/~sdlee |
`'
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS export
John == John Minnihan [EMAIL PROTECTED] writes:
John Why use export? Overnite builds are very common and needn't
John cause you any undue pain. Use a disposable build tag (aka
John release tag), such as Application__Overnite__12345, where
John the digits are an incrementing build number that is
John guaranteed to be unique. Then simply 'cvs co -r
John Application__Overnite__12345' to get the sources for your
John build. This is straightforward to automate and creates a
John visually informative trail in the logs. Tags are cheap -
John tag early, tag often.
I consider these periodically made tags costly, as I can
cvs export/co -D 3 months ago ...
easily. And this is virtually free. Tags also makes fills the output
of cvs log -h with rubbish.
--
Lee Sau Dan §õ¦u´°(Big5)~{@nJX6X~}(HZ)
..
| e-mail: [EMAIL PROTECTED]http://www.csis.hku.hk/~sdlee |
`'
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS a Web site
Jason Purdy [EMAIL PROTECTED] writes: What is a good scheme of automating synchronization between a CVS repository and a Web site [...] 2) Create 'trigger' scripts which would be triggered when the developer 'commit'ed their changes, which would also affect the changes on the Web site directories. Yes, like that. It's documented in the manual. Try searching for Keeping a checked out copy. You could tweak the approach therein to keep an exported copy instead. Also, it would be a *really, really good idea* to run multiple copies of the web server, one for each developer sandbox, each running on a private high-numbered port. That way, the developers can browse and debug their sandboxes before committing. -- Pierre Asselin Westminster, Colorado -= Posted via Newsfeeds.Com, Uncensored Usenet News =- http://www.newsfeeds.com - The #1 Newsgroup Service in the World! -== Over 80,000 Newsgroups - 16 Different Servers! =- ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
case changing [was: list of editors in notify]
On Thu, Oct 18, 2001 at 10:06:44AM -0400, Michael Santos wrote: Is the list of editors available to the script as a CVS variable (like $USER)? Otherwise, it appears the only way would be to parse .../CVS/fileattr from the script run from notify, grabbing the file path from the notify message. To answer my own question, the above works. My next question: has the issue with changes in capitalization of filenames between Windows and Unix client/servers been resolved (e.g., under Windows, rename file.txt = File.txt, commit File.txt)? What is the suggested work around for it? I can prevent capitalization changes by using a pre-commit check but I'm wondering if anyone has a better way. -- Michael Santos [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: CVS export
-Original Message- From: Lee Sau Dan [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 18, 2001 12:23 PM To: [EMAIL PROTECTED] Subject: Re: CVS export This message uses a character set that is not supported by the Internet Service. To view the original message content, open the attached message. If the text doesn't display correctly, save the attachment to disk, and then open it using a viewer that can display the original character set. This is how your message came across in Microsoft Outlook (no, it wasn't my idea to use it companywide). Posting in a form that people can't read is not going to help them respond to you. Please make sure you're posting in straight ASCII. Everybody can read that easily. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS export
Lee Sau Dan writes: I usually say -D now. I know -D today would work, too, but I'm not sure if it means midnight (00:00) of today. It means the start of today (00:00), which is not the same as now. -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 export
[ On , October 18, 2001 at 19:22:33 (+0200), Lee Sau Dan wrote: ] Subject: Re: CVS export easily. And this is virtually free. Tags also makes fills the output of cvs log -h with rubbish. Something like that is only rubbish if it doesn't mean anything to you. To me those dates you would use are just rubbish since I can't know for sure that they represent a well known boundary or milestone in development. To me the tags I would use represent very well known points in the temporal state of the repository -- points that don't rely on having to remember (or write down in some other place) a timestamp. -- Greg A. Woods +1 416 218-0098 VE3TCP [EMAIL PROTECTED] [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS export
[ On Thursday, October 18, 2001 at 11:49:52 (-0700), John Minnihan wrote: ] Subject: Re: CVS export building =//= releasing, especially when the build is already understood to be an 'overnite' which is at the very bottom of the food chain. Of course not -- _BUT_ that's why I qualified my comments with questions about why/why/how the nightly builds were to be used. If they're actually used to obtain snapshots from which further testing and perhaps even decisions about release milestones are made, then having tags and using cvs export will be the better way to go. Also, if your nightly builds are used to test your build and release process itself then cvs export is just as necessary then as it will be when you make the actual release. Use of 'cvs export' to collect sources that are used to produce a build is almost never necessary. On the contrary -- cvs export is the best way to guarantee that a source release is exactly what should be in the release (and of course one would want to build it to ensure that it's a viable release). -- Greg A. Woods +1 416 218-0098 VE3TCP [EMAIL PROTECTED] [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Why can't root check in files?
[ On Thursday, October 18, 2001 at 18:19:49 (GMT), Kaz Kylheku wrote: ] Subject: Re: Why can't root check in files? You will get better version control if you just edit your /etc directory in place and do daily backups of it instead of fussing about with CVS. That's for darn sure! (and on the *BSD systems they nightly system jobs even do some form of backups for you!) -- Greg A. Woods +1 416 218-0098 VE3TCP [EMAIL PROTECTED] [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Soft link in CVS
* Eli Eaton ([EMAIL PROTECTED]) [011014 11:45]: Does anyone know of the best way to support soft link in UNIX in a CVSROOT ? Put one there? I want some files that reside in one directory to be linked to files exist in other directory. When I checkout/update/commit the files in any of the directories it will update the second one. It'll have that effect. But, as many have stated before, doing that can cause _serious_ problems with locking and other actions. jon -- .Jonathan J. Miner--Division of Information Technology. |[EMAIL PROTECTED] University Of Wisconsin - Madison| |608/262.9655 Room 3149 Computer Science| `-' Remember though that THERE IS NO GENERAL RULE FOR CONVERTING A LIST INTO A SCALAR. -- Larry Wall in the perl man page (96) ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Using LDAP to authenticate cvs logins.
Can anyone point me to a HOWTO or provide any information on how you can setup CVS to use an LDAP server for client authentication. TIA, - Mike D. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS export
[EMAIL PROTECTED] wrote: [ On Thursday, October 18, 2001 at 11:49:52 (-0700), John Minnihan wrote: ] Subject: Re: CVS export building =//= releasing, especially when the build is already understood to be an 'overnite' which is at the very bottom of the food chain. Of course not -- _BUT_ that's why I qualified my comments with questions about why/why/how the nightly builds were to be used. If they're actually used to obtain snapshots from which further testing and perhaps even decisions about release milestones are made, then having tags and using cvs export will be the better way to go. Also, if your nightly builds are used to test your build and release process itself then cvs export is just as necessary then as it will be when you make the actual release. Use of 'cvs export' to collect sources that are used to produce a build is almost never necessary. On the contrary -- cvs export is the best way to guarantee that a source release is exactly what should be in the release (and of course one would want to build it to ensure that it's a viable release). In all the years I've used CVS, I've institutionalized use of 'cvs export' only briefly at one client. And that was only to satisfy some nimrod (who didn't understand cvs) who screamed - repeatedly - get rid of all these CVS files!. Presence - or absence - of the CVS admin structure hasn't had the slightest impact (positively or negatively on its own merit)on the success of failure of any of the thousands of releases I've produced. Period. 'cvs co' with a known tag is the way to go. -- John Minnihan mailto:[EMAIL PROTECTED] http://www.freepository.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS and Delphi
I'm not quite sure what you mean by linking your components with source code. However, I may provide some ideas on managing Delphi files with CVS. I think there are three types of files in a Delphi project: 1. Pascal Code (*.pas) 2. Form Definitions (*.dfm) 3. Data Modules (also *.dfm) All *.pas files are text, and thus easily submitted into CVS. For *.DFM files, I ask my developers to set them as text DFM, and simply check them in in CVS. However, I don't have many branches at the moment. And so far, we have not had the need to merge between branches. When merging is required, it will be a good practice to pay extra attention in *.DFM files. Hope this helps. If anyone else have a better tips, please jump in. At 15:10 18/10/2001 +0100, you wrote: Is anyone using CVS to store Borland Delphi source code, as I am unsure how to link our versions of components with versions of source code ? Andrew Oates Tel: +44 (0) 1959 579000 Fax: +44 (0) 1959 579039 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS export
[ On Thursday, October 18, 2001 at 20:34:13 (-0700), John Minnihan wrote: ] Subject: Re: CVS export In all the years I've used CVS, I've institutionalized use of 'cvs export' only briefly at one client. And that was only to satisfy some nimrod (who didn't understand cvs) who screamed - repeatedly - get rid of all these CVS files!. The reasons for using cvs export have (almost) nothing at all to do with getting rid of the CVS administrative subdirectories and files. -- Greg A. Woods +1 416 218-0098 VE3TCP [EMAIL PROTECTED] [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
