k...@freefriends.org (Karl Berry) writes: > What I mean - I wouldn't mind commiting gnulib stuff to VCS, but only > if I can omit files generated by autoreconf. > > FWIW, that is exactly what I do for Texinfo. It helps my contributors > to not spend time dealing with gnulib, and it helps me because it avoids > gnulib-skew differences between me and my contributors. > > Of course, you have to be careful not to commit (and to .vcignore) the > files generated by make, such as lib/foo.h when lib/foo.in.h exists. > > Feel free to peruse the Texinfo source repo > (https://savannah.gnu.org/cvs/?group=texinfo) if you're interested. > > >From reading the manual, I got the impression that it is strictly the > either-or approach, > > I think the manual (node "VCS Issues") could mention this "middle road" > as a possibility. As far as I can see, you are correct that it only > describes the all-or-nothing approach now. > > If the idea acceptable to the other gnulib folks, I could try to write a > patch for it.
Please do, I'm using the same approach as you do and I think it should be supported. One of my reasons is that bootstrap cannot handle multiple gnulib instances in a project. This middle road approach supports that. /Simon
