Re: Can somebody explain the benefits of .d directories
On 11/27/2017 04:31 PM, Nicolas George wrote:
This is the reason that the .d directories were done. However, I also
find that for manual configuration, I do almost exactly the same thing.
For example, if/when I decide to add a third party repository to my
sources.list files, I usually do it by adding a file to sources.list.d,
rather than editing the sources.list file. This makes it much easier for
me to locate specific things in my repository lists. I simply do an ls
/etc/sources.list.d and can quickly locate the snippet responsible for a
particular repository. I have used this strategy for other software
which has a configuration file that can be pretty large. I don't have
to manually search through the file to find the one or two lines I'm
I have an honest question which is dead-simple: Why do we have ".d" directories
To allow packages to provide configuration snippets. Packages work at
the file level, they provide sets of files. When a package needs to
provide a configuration snippet, for example when it provides a plugin
for another software, it does so by providing a file. When the package
is upgraded, the normal handling of configuration files can be applied.
Modifying a monolithic configuration file would be much more fragile.