Hi Bruno, Am Sa., 3. Apr. 2021 um 12:05 Uhr schrieb Bruno Haible <br...@clisp.org>:
> Hi Marc, > > > If Gnulib is going to be extended to support the second option as well > > That's what I'm suggesting, because the second way to manage files appears > to be the majority one. > > > I am not yet sure how. The problem is that the same source tree would > have to > > support both options to support both kinds of developers. > > No, when .gitignore lists all built files, this holds for all developers. > Right. This is even more fundamental than my point about "bootstrap.conf". > In a project where some developers want the first approach and some want > the second one, the built files need to be listed in the .git/info/exclude > file, not in .gitignore. But since .git/info/exclude is not shared among > developers, it is tedious for every developer to maintain their own > .git/info/exclude list. Therefore I don't think this "mixed" model is > widely used. > Would it do much harm if ".gitignore" included all built files even for developers that work in a dedicated build tree? Adding all built files automatically to ".gitignore" may, however, be non-trivial because file extensions (like "$EXE") can vary from system to system.
