> >>> I thought the consensus of the discussion was that this was not
> >>> necessary. It sure doesn't strike me as a good idea.
>
> > Also, keep in mind that in the end most folks will be building
> > under MinGW using a release tarball, that has those output files.
> > We haven't gotten a MinGW release yet, so they have to build all
> > the stuff.
>
> Well, that's a fair argument, but why don't you get Marc to set up
> nightly snapshots for the WIN32_DEV branch? That only costs cycles
> in the short term. Polluting CVS with updates to derived files will
> cost us CVS storage forever.
Um, why not just have someone with local CVSROOT access just rm -f the
,v file when the WIN32_DEV branch ceases to be useful? In the
meantime, have the flex/bison files in CVS. Few will notice or care
in the meantime other than possibly CVSup administrators. Just a
thought.
-sc
--
Sean Chittenden