[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Make cvs ignore some changes in files

From: Noel Yap
Subject: RE: Make cvs ignore some changes in files
Date: Thu, 22 Aug 2002 07:12:28 -0700 (PDT)

--- Frederic Brehm <address@hidden> wrote:
> I wrote:
> >The generated files don't need to be revision
> controlled, but they need to 
> >be available to people or tools who cannot run the
> tool that generates the 
> >files. The most convenient way to make the files
> available is to put them 
> >into the repository alongside the other files that
> are also needed. The 
> >side effect of this is that the files become
> revision controlled.
> but then I wrote:
> >  --- If these are different, then Makefile.cache
> is replaced with
> >     the new version. The next cvs commit will
> commit the new
> >     Makefile.cache along with any new or changed
> source files.
> I just realized that this explains why, in this
> case, the files *must* be 
> revision controlled. The new version of
> Makefile.cache corresponds to the 
> new versions of the other files in the directory.

I don't understand, if Makefile.cache has to be in
synch with the other files:
1. Why are there systems that are able to commit, but
can't build Makefile.cache?
2. Why would you not want to commit Makefile.cache
once it's regenerated?
3. Why can't the build system just generate
Makefile.cache without it being versioned?


Do You Yahoo!?
HotJobs - Search Thousands of New Jobs

reply via email to

[Prev in Thread] Current Thread [Next in Thread]