On 2019-06-13, Quentin Rameau <[email protected]> wrote: > Hello Michael, > >> Also, add rule to regenerate in case executable list changes. >> --- >> Any objection to this? > > I'm not really keen on pushing this file to the source history, I think > this should be kept separate, this is a user-side feature.
What's the downside to having it checked into the repository? Are there any reasons why a user wouldn't want this feature? Personally, I want it in every clone of sbase I make, and I imagine most other people want this as well. It is annoying to have `git status` scroll my changes off the screen due to all the build artifacts. > But having a rule un the Makefile, as you did, is a good compromise > there, if the user wants it, he can have it with little additionnal > effort. > > So I'd be for pushing the Makefile rule, not committing the actual file > into the development history The place for user-specific and repository-specific ignored files is .git/info/exclude. But in general, we don't know the location of the .git directory, so we'd probably have to use some git command to figure out exactly where to put it.
