Hi everyone,
the current IncludeConfig implementation has some issues, especially
for distributers:
All files in the directory as specified by $IncludeConfig are included.
This means, temp files like *~ *.bak etc that are left behind by
editors, or stuff like *.rpmsave or *.dpkg-old/*.dpkg-new.
This is obviously unfortunate.
How shall we solve this?
1.) I patched the Debian package to only include files ending with
*.conf. If we document that properly this is imho an acceptable
solution.
2.) Implement an internal blacklist of endings that are ignored (see above)
3.) Instead of hardcoding the file ending to *.conf (as in 1.), use
the same syntax as e.g. apache, which allows to specify shell globs:
example:
Include /etc/apache2/conf.d/*.conf
What do you think?
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
the current IncludeConfig implementation has some issues, especially
for distributers:
All files in the directory as specified by $IncludeConfig are included.
This means, temp files like *~ *.bak etc that are left behind by
editors, or stuff like *.rpmsave or *.dpkg-old/*.dpkg-new.
This is obviously unfortunate.
How shall we solve this?
1.) I patched the Debian package to only include files ending with
*.conf. If we document that properly this is imho an acceptable
solution.
2.) Implement an internal blacklist of endings that are ignored (see above)
3.) Instead of hardcoding the file ending to *.conf (as in 1.), use
the same syntax as e.g. apache, which allows to specify shell globs:
example:
Include /etc/apache2/conf.d/*.conf
What do you think?
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?