From: Andy Wingo <wingo@igalia.com>
To: "Huang, Ying" <huang_ying_caritas@163.com>
Cc: guix-devel@gnu.org, Alex Kost <alezost@gmail.com>
Subject: Re: [PATCH 1/2] build: union: Add create-all-directory? parameter to union-build
Date: Fri, 24 Feb 2017 14:32:41 +0100 [thread overview]
Message-ID: <877f4f7lza.fsf@igalia.com> (raw)
In-Reply-To: <87tw7jn4mo.fsf@163.com> (Ying Huang's message of "Fri, 24 Feb 2017 20:40:47 +0800")
Hi :)
On Fri 24 Feb 2017 13:40, "Huang, Ying" <huang_ying_caritas@163.com> writes:
>> (define (union output inputs)
>> (match inputs
>> ((input)
>> - ;; There's only one input, so just make a link.
>> - (symlink* input output))
>> + ;; There's only one input, so just make a link unless create-all-directory?
This comment should be a full sentence ending with a period, with line
wrapped at 72 columns.
>> + (if (and create-all-directory? (file-is-directory? input))
>> + (union-of-directories output inputs)
>> + (symlink* input output)))
What's the use case? Something that can handle some symlinks in the
tree but not all symlinks in the tree? I think this patch is a bad idea
for union-build because it has a strange effect that's hard to describe
up and down the union (both at the root and at branch directories). I
think it's probably a better idea to go for something more fit to your
purpose and only pull it into union-build once you see yourself needing
it more than once. IMO anyway :)
Andy
next prev parent reply other threads:[~2017-02-24 13:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 0:44 [PATCH 1/2] build: union: Add create-all-directory? parameter to union-build huang_ying_caritas
2017-02-18 0:44 ` [PATCH 2/2] guix: profiles: create fonts.dir/scale for all fonts directories huang_ying_caritas
2017-02-24 12:40 ` [PATCH 1/2] build: union: Add create-all-directory? parameter to union-build Huang, Ying
2017-02-24 13:32 ` Andy Wingo [this message]
2017-02-25 1:03 ` Huang, Ying
2017-02-24 14:02 ` Danny Milosavljevic
2017-02-24 22:13 ` Mark H Weaver
2017-02-25 12:43 ` Huang, Ying
2017-02-27 9:06 ` Danny Milosavljevic
2017-03-03 1:25 ` Mark H Weaver
2017-02-25 1:05 ` Huang, Ying
2017-02-25 12:30 ` Huang, Ying
2017-02-26 8:23 ` 宋文武
2017-02-27 11:27 ` Huang, Ying
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=877f4f7lza.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=huang_ying_caritas@163.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/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).