On 11/27/2017 04:31 PM, Nicolas George wrote:
Hans-Peter (2017-11-27):
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
prov
Hans-Peter writes:
> I have an honest question which is dead-simple: Why do we have ".d"
> directories, such as "sources.d" or "grub.d", note that with grub, the
> defaults are in another directory tree - this is simply beyond insane.
Your question there seems less than an honest enquiry – askin
On Mon, Nov 27, 2017 at 05:09:49PM -0500, Hans-Peter wrote:
>I have an honest question which is dead-simple: Why do we have ".d"
>directories, such as "sources.d" or "grub.d", note that with grub, the
>defaults are in another directory tree - this is simply beyond insane.
>(Sorry to
Hans-Peter (2017-11-27):
> 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
4 matches
Mail list logo
