@mollekopf, This will make my life harder. I can't make src/database/seeds a link to dir in config.demo/config.dev. Rewriting this file will make a problem to use git diff/git commit or whatever.

In rKc99e8be93682770d130ddcf6c3f62d3f407cbfc1#558094, @machniak wrote:

@mollekopf, This will make my life harder. I can't make src/database/seeds a link to dir in config.demo/config.dev. Rewriting this file will make a problem to use git diff/git commit or whatever.

Atm this only affects the kolabnow config I think, so our options are:

• Add the dummy seeder to the kolabnow config
• Ignore the changes via .gitignore
• If it's just the directory that is the issue (not the seeder), then a .gitkeep file would be enough.

The most generic approach seems to me .gitignore/.gitkeep.

tbh, I'm not sure what the best approach is. We'll face the same issue when we e.g. include a configuration file in the overlay that also exists in the base, but I don't think we should limit ourselves to never overriding files that exist in the base.

Whenever there are such conflicts we have the issues that:

• The modifications show up in git diff
• A git pull is blocked due to modifications
• A new file added to git will overwrite the one that was created by configure.sh (at least that's what I believe just happened to me).

See https://git.kolab.org/D4063