This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: Non-source files in CVS
Jost Boekemeier <jostobfe@calvados.zrz.TU-Berlin.DE> writes:
> Marius Vollmer <mvo@zagadka.ping.de> writes:
>
> > I think we can use `$CVSROOT/CVSROOT/cvsignore' and leave .cvsignore
> > to the user. It looks like Guile has its own repository, so it should
> > be no major problem that `$CVSROOT/CVSROOT/cvsignore' is
> > per-repository and not per-module.
>
> Can cvs users access the file $CVSROOT/CVSROOT/cvsignore by using cvs
> commands? If not, how can you tell the users which files are created
> by the build process and should be ignored?
Yes; just check out the CVSROOT module.
> Of course I can run cvs co, capture the state of all subdirs compare
> them with the state after configure/make and create my own
> .cvsignore's by using a script.
The built files are reasonably well-defined by the tools that build
them. Plus, the cvsignore file only needs to be updated once, and when
new scripts/tools are used to build the sources.
Greg