Ticket #3739 (new defect)

Opened 3 years ago

Last modified 3 years ago

.gitignore : build process should not left any modified or untracked files

Reported by: sorin Owned by:
Priority: major Milestone: Future Releases
Component: mc-core Version: master
Keywords: Cc:
Blocked By: Blocking:
Branch state: no branch Votes for changeset:


The build process should not left any modified or untracked files.

All temporary or output files should be covered by .gitignore file, but currently there are lots of files left after doing configure and build steps.

While this is fixed we can also introduce an additional build step that check if new files are left over and that would fail the build if unknown files are detected.

Easy to check: do a git check

Change History

comment:1 Changed 3 years ago by zaytsev

Hmmm, I don't see any non-ignored files in my checkout, maybe you are building in-place instead of doing a proper VPATH build, and so some build artifacts are mixing in.

Anyways, what's much worse, is that there is no single clean documented .gitignore file in the root directory of the repository, but many .gitignore files spread all over the place, partly containing wrong / overlapping / too broad / obsolete entries.

Cleaning this up properly is tons of hard work, but I don't think it's actually useful. Much easier solution would be to declare that anyone not building release versions should do VPATH builds, and if build artifacts leak outside build directory, then it's a problem.

This would allow to simplify and shorten .gitignore patterns dramatically...

Note: See TracTickets for help on using tickets.