From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: luangruo@yahoo.com, masm+emacs@masm11.me, emacs-devel@gnu.org
Subject: Re: gsettings.m4 copyright
Date: Mon, 03 Jan 2022 19:26:14 +0200 [thread overview]
Message-ID: <83y23wbuix.fsf@gnu.org> (raw)
In-Reply-To: <jwvsfu4x15c.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 03 Jan 2022 11:03:13 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Yuuki Harano <masm+emacs@masm11.me>, luangruo@yahoo.com,
> emacs-devel@gnu.org
> Date: Mon, 03 Jan 2022 11:03:13 -0500
>
> >> > 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.
I guess you mean we don't _need_ their permission.
Except that in Emacs (and other projects that care about attribution
and copyright assignments), we do.
> > 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?
That's not the problem I'm worried about.
next prev parent reply other threads:[~2022-01-03 17:26 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
2022-01-03 17:26 ` Eli Zaretskii [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y23wbuix.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=masm+emacs@masm11.me \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).