Re: cvs update blew away configure; and I don't have autoconf

2001-01-29 Thread Didier Verna
Ronan Waide wrote: On January 26, [EMAIL PROTECTED] said: Fair enough. Modifying .cvsignore to include configure seems to have solved the problem. I guess I don't grok CVS well enough to understand the problem but I don't want to cause any pain. I wonder if adding configure to

Re: cvs update blew away configure; and I don't have autoconf

2001-01-26 Thread Ronan Waide
On January 26, [EMAIL PROTECTED] said: Actually, I do have autoconf, but not a sufficiently recent version to generate the configure script and I don't want to wait for my sysadmin to install it. Could someone please add the configure script to the repository? All other CVS repositories

Re: cvs update blew away configure; and I don't have autoconf

2001-01-26 Thread David S. Goldberg
Fair enough. Modifying .cvsignore to include configure seems to have solved the problem. I guess I don't grok CVS well enough to understand the problem but I don't want to cause any pain. I wonder if adding configure to .cvsignore in the repository would be appropriate, though since it's

Re: cvs update blew away configure; and I don't have autoconf

2001-01-26 Thread Raymond Scholz
Ronan Waide [EMAIL PROTECTED] schrieb: It's a simple rule: generated files shouldn't be in CVS, because that way lies pain and hassle. Does this also apply to the gzipped tar archive of BBDB 2.20 I find in the html directory? :-) Cheers, Ray -- Raymond Scholz - [EMAIL PROTECTED] - PGP -

Re: cvs update blew away configure; and I don't have autoconf

2001-01-26 Thread Ronan Waide
On January 26, [EMAIL PROTECTED] said: Ronan Waide [EMAIL PROTECTED] schrieb: It's a simple rule: generated files shouldn't be in CVS, because that way lies pain and hassle. Does this also apply to the gzipped tar archive of BBDB 2.20 I find in the html directory? :-) Cheers, Ray

Re: cvs update blew away configure; and I don't have autoconf

2001-01-26 Thread Ronan Waide
On January 26, [EMAIL PROTECTED] said: Fair enough. Modifying .cvsignore to include configure seems to have solved the problem. I guess I don't grok CVS well enough to understand the problem but I don't want to cause any pain. I wonder if adding configure to .cvsignore in the repository