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
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 (gnus, w3 etc) provide the
configure script.
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
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
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 -
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
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
