Am 11.05.2018 um 15:21 schrieb Paul Jakma:
> logind.conf has a GPL header, as do things like getty@.service.
>
> If I needed to make changes to logind.conf, and wanted to bundle a
> modified logind.conf with a GPL-incompatible application, is that
> allowed?
that's not how you are supposed to
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
Hi,
On Fri, 11 May 2018, Zbigniew Jędrzejewski-Szmek wrote:
On Fri, May 11, 2018 at 02:21:30PM +0100, Paul Jakma wrote:
Hi,
logind.conf has a GPL header, as do things like getty@.service.
An LGPL header actually, *library*.
Ah yes. Not quite sure what that will mean in the context of a
On Fri, May 11, 2018 at 02:21:30PM +0100, Paul Jakma wrote:
> Hi,
>
> logind.conf has a GPL header, as do things like getty@.service.
An LGPL header actually, *library*.
All you need to do, is to keep the possibility to modify/destribute
that .conf file.
> If I needed to make changes to
On Fri, 11 May 2018, Reindl Harald wrote:
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
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
