From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Specifying package patches in a more convenient form
Date: Sat, 09 Apr 2016 16:43:11 +0200 [thread overview]
Message-ID: <87potyn8qo.fsf@gnu.org> (raw)
In-Reply-To: <87d1q0sey7.fsf@gmail.com> (Alex Kost's message of "Fri, 08 Apr 2016 11:05:36 +0300")
Alex Kost <alezost@gmail.com> skribis:
> Andy Wingo (2016-04-07 13:08 +0300) wrote:
>
>> On Thu 07 Apr 2016 11:52, Alex Kost <alezost@gmail.com> writes:
>>
>>> Eric Bavier (2016-04-06 17:57 +0300) wrote:
>>>
>>>> On Wed, 06 Apr 2016 15:13:47 +0300
>>>> Alex Kost <alezost@gmail.com> wrote:
>>> [...]
>>>>> > + "1lgghck46p33z3hg8dnl76jryig4fh6d8rhzms837zp7x4hyfkv4"))
>>>>> > + (patches (map search-patch '("ttfautohint-source-date-epoch.patch")))))
>>>>>
>>>>> Since it's just a single patch, I don't see a reason to use 'map' here.
>>>>
>>>> Just that it's less to change if more patches are added later. The
>>>> same has been used in other packages.
>>>
>>> I strongly disagree with this policy. More patches may never be added,
>>> but mapping through a list of a single element looks redundant for me.
>>
>> What if the "patches" field just applied `search-path' to each of the
>> items in the list if the path is not absolute? Use
>> `absolute-file-name?' to check if this is needed or not.
>
> I think it is a good choice that 'patches' field takes a list of file
> names. For example, currently a user can do:
>
> (patches (find-my-patches "package-name"))
>
> With what you suggest, it would not be possible.
It would still be possible, provided ‘find-my-patches’ returns absolute
file names. But yeah, there would always be this extra pass of
guesswork under the hood.
Ludo’.
next prev parent reply other threads:[~2016-04-09 14:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 4:32 [PATCH 1/9] gnu: Add ttfautohint ericbavier
2016-04-06 4:32 ` [PATCH 2/9] gnu: Add woff-tools ericbavier
2016-04-07 6:18 ` Efraim Flashner
2016-04-07 14:25 ` Eric Bavier
2016-04-13 21:37 ` Ludovic Courtès
2016-04-06 4:32 ` [PATCH 3/9] gnu: Add ttf2eot ericbavier
2016-04-07 6:24 ` Efraim Flashner
2016-04-07 14:30 ` Eric Bavier
2016-04-08 3:49 ` Eric Bavier
2016-04-13 21:39 ` Ludovic Courtès
2016-04-06 4:32 ` [PATCH 4/9] gnu: Add brotli ericbavier
2016-04-13 21:44 ` Ludovic Courtès
2016-04-06 4:32 ` [PATCH 5/9] gnu: Add woff2 ericbavier
2016-04-06 4:32 ` [PATCH 6/9] gnu: fontforge: Make SVG builds reproducible ericbavier
2016-04-06 17:36 ` Leo Famulari
2016-04-06 17:44 ` Eric Bavier
2016-04-06 17:56 ` Leo Famulari
2016-04-06 4:32 ` [PATCH 7/9] gnu: Add font-fantasque-sans ericbavier
2016-04-06 4:33 ` [PATCH 8/9] gnu: fontforge: Use modify-phases ericbavier
2016-04-06 4:33 ` [PATCH 9/9] gnu: fontforge: Install 'showttf' tool ericbavier
2016-04-06 12:13 ` [PATCH 1/9] gnu: Add ttfautohint Alex Kost
2016-04-06 14:57 ` Eric Bavier
2016-04-07 9:52 ` Specifying package patches in a more convenient form Alex Kost
2016-04-07 10:08 ` Andy Wingo
2016-04-07 14:41 ` Eric Bavier
2016-04-08 8:05 ` Alex Kost
2016-04-09 14:43 ` Ludovic Courtès [this message]
2016-04-07 21:54 ` Ludovic Courtès
2016-04-09 8:22 ` Alex Kost
2016-04-09 11:42 ` Andreas Enge
2016-04-09 16:40 ` Alex Kost
2016-04-13 21:40 ` [PATCH 1/9] gnu: Add ttfautohint Ludovic Courtès
2016-04-13 21:36 ` Ludovic Courtès
2016-04-14 14:43 ` Eric Bavier
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=87potyn8qo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--cc=guix-devel@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).