GPL and unit/conf files

[h.reindl@xxxxxxxxxxxxx (Reindl Harald)]

Am 11.05.2018 um 15:48 schrieb Paul Jakma:
> On Fri, 11 May 2018, Reindl Harald wrote:
> 
>> that's not how you are supposed to work with systemd-configs
> 
> Agreed. The technicalities in the app concerned of how it delivers these
> settings probably could be done better here, but that's another question
> / problem.
> 
>> /usr/lib/systemd/ has the same structure as /etc/systemd/
>>
>> * /usr/lib/systemd -> package files
>> * /etc/systemd -> local overrides
>>
>> [root at srv-rhsoft:~]$ cat /etc/systemd/logind.conf.d/logind.conf
>> [Login]
>> KillUserProcesses=no
> 
> The question remains, if I deliver a file that extends/modifies the
> systemd config file with the GPL header, can I ship such a file bundled
> with a GPL-incompatible app?
> 
> If I do it via an override file, is that a derived work of the GPL?

no it is not - it's just a config file using as subset of options

if that would be the case you couldn't shop any systemd-unit with your
application

> My wider point here is that maybe the GPL isn't the right/most
> convenient licence header to put on settings files. ;)

maybe, but no issue since you don't need to touch them