GPL and unit/conf files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?

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

regards,
-- 
Paul Jakma | paul at jakma.org | @pjakma | Key ID: 0xD86BF79464A2FF6A
Fortune:
If you want to travel around the world and be invited to speak at a lot
of different places, just write a Unix operating system.
 	-- Linus Torvalds


[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux