From: Yuuki Harano <masm+emacs@masm11.me>
To: eliz@gnu.org
Cc: luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: gsettings.m4 copyright
Date: Tue, 04 Jan 2022 00:59:33 +0900 (JST) [thread overview]
Message-ID: <20220104.005933.1606504355738130153.masm@luna.pink.masm11.me> (raw)
In-Reply-To: <8335m4dfbp.fsf@gnu.org>
On Mon, 03 Jan 2022 17:11:38 +0200,
Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Mon, 03 Jan 2022 16:29:21 +0200
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: luangruo@yahoo.com, emacs-devel@gnu.org
>>
>> 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?
>
> Actually, that file does little more except rewriting some rules in
> Makefile.in, is that so? If so, can't we do that using the GNU Make
> ifdef/ifeq conditionals, like we do with native-compilation specific
> fragments? Then perhaps the configure.ac stuff to support that could
> be very small, limited to defining some Make macro.
>
> Does this make sense?
Thank you.
I'll try to do in that way tomorrow.
--
Yuuki Harano
next prev parent reply other threads:[~2022-01-03 15:59 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 [this message]
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
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=20220104.005933.1606504355738130153.masm@luna.pink.masm11.me \
--to=masm+emacs@masm11.me \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
/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).