From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Yuuki Harano <masm+emacs@masm11.me>,
luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: gsettings.m4 copyright
Date: Mon, 03 Jan 2022 11:03:13 -0500 [thread overview]
Message-ID: <jwvsfu4x15c.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83a6gcdha6.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 03 Jan 2022 16:29:21 +0200")
>> > Jeff and Yuuki, would you please tell us how you got this file and who
>> > has the copyright to its code?
>> I copied /usr/share/aclocal/gsettings.m4 in my PC.
> That file is installed when you install Glib, so you basically copied
> it from Glib without their permission.
Since it's under the LGPL we do have their permission.
> At this point, I think we should consider removing the file and
> rewriting the tests it performs in configure.ac, in as different a
> form from gsettings.m4 as possible. Is that feasible?
Is there a specific problem with the file being LGPL?
IIUC the LGPLv2.1 is compatible with GPLv3 (not sure about GPL>3), so
I don't think we have a license problem right now. Is the problem
limited to "we don't own its copyright" (i.e. something which we impose
on ourselves and could thus choose to ignore)?
Stefan
next prev parent reply other threads:[~2022-01-03 16:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r19pgl3x.fsf.ref@yahoo.com>
2022-01-03 10:38 ` gsettings.m4 copyright Po Lu
2022-01-03 12:53 ` Eli Zaretskii
2022-01-03 12:56 ` Po Lu
2022-01-03 13:02 ` Eli Zaretskii
2022-01-03 13:28 ` Po Lu
2022-01-03 13:39 ` Yuuki Harano
2022-01-03 14:29 ` Eli Zaretskii
2022-01-03 15:11 ` Eli Zaretskii
2022-01-03 15:59 ` Yuuki Harano
2022-01-04 8:35 ` Yuuki Harano
2022-01-04 13:29 ` Eli Zaretskii
2022-01-03 16:03 ` Stefan Monnier [this message]
2022-01-03 17:26 ` Eli Zaretskii
2022-01-03 23:56 ` Richard Stallman
2022-01-04 3:31 ` Eli Zaretskii
2022-01-04 3:48 ` Stefan Kangas
2022-01-05 3:53 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvsfu4x15c.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=masm+emacs@masm11.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.