[systemd-devel] [RFC][PATCH] conf-parser: distinguish between multiple sections with the same name

[Kay Sievers]

On Wed, Nov 20, 2013 at 3:05 PM, Thomas Bächler <thomas at archlinux.org> wrote:
> Am 20.11.2013 15:02, schrieb Tom Gundersen:
>>> what does this mean? Does it override the value of the first section,
>>> the second section or does it create a new section?
>>
>> Yeah, in this case it would not make sense. However, this stuff is
>> opt-in only, and unit files don't opt-in (currently nothing does). For
>> the use-case I have in mind we won't allow partial overrides and
>> probably not even drop-ins/includes.
>
> So, we'd have inconsistent config file syntax across systemd? Some
> section types override/extend when we write them more than once, some
> section types create new instances?

We have contradicting domain specific stuff and rules everywhere.

The network files are a stream of files to read and stop at the first
match, file names do not matter at all besides the ordering of apply.

With unit files we have one set of keys, the file name is the key to
lookup the entire set and the drop-ins.

Drop-in for a flow of unnamed files make not much sense, I think.

> I like the idea of assigning unique names to section "instances" much more.

We could still support/allow them to be named, but not sure why we
would need to require them.

Kay