From: Mathieu Lirzin <mthl@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/2] build: Move included files to subdirectories.
Date: Fri, 15 Apr 2016 00:55:57 +0200 [thread overview]
Message-ID: <8737qnx0jm.fsf@gnu.org> (raw)
In-Reply-To: <87shyohymg.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 14 Apr 2016 19:46:31 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Eric Bavier <ericbavier@openmailbox.org> skribis:
>>
>> I don't prefer the "local.mk" convention. It becomes
>> non-obvious that the file is input for Automake, and the name loses any
>> descriptive power.
>
> I have mixed feelings (notably because file names in those .mk files
> remain relative to $top_srcdir, which can be confusing and will make M-/
> useless).
I didn't know about M-/ :)
To emphasize how the file names relate to the current directory of the
‘Makefile’ snippet, we could use ‘%reldir%’ or ‘%D%’ like describe in:
https://www.gnu.org/software/automake/manual/automake.html#Include
Moreover this would makes the future move/rename of directories less
troublesome.
WDYT?
--
Mathieu Lirzin
next prev parent reply other threads:[~2016-04-14 22:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 16:18 [PATCH 0/2] Clean repository top-level directory Mathieu Lirzin
2016-04-03 16:18 ` [PATCH 1/2] build: Move included files to subdirectories Mathieu Lirzin
2016-04-04 2:36 ` Eric Bavier
2016-04-14 17:46 ` Ludovic Courtès
2016-04-14 22:55 ` Mathieu Lirzin [this message]
2016-04-16 22:54 ` Ludovic Courtès
2016-05-21 21:41 ` Mathieu Lirzin
2016-05-22 20:33 ` Ludovic Courtès
2016-04-03 16:18 ` [PATCH 2/2] build: Move environment scripts to 'build-aux' directory Mathieu Lirzin
2016-04-03 17:05 ` Alex Kost
2016-04-03 17:18 ` Mathieu Lirzin
2016-04-03 21:56 ` Alex Kost
2016-04-03 18:19 ` Leo Famulari
2016-04-03 19:19 ` Mathieu Lirzin
2016-04-14 17:48 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737qnx0jm.fsf@gnu.org \
--to=mthl@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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/guix.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).