all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Oleg Pykhalov <go.wigust@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 30433@debbugs.gnu.org, 30433-done@debbugs.gnu.org
Subject: [bug#30433] [PATCH] gnu: Add epipe.
Date: Thu, 15 Feb 2018 20:47:32 +0300	[thread overview]
Message-ID: <87a7waxhzf.fsf@gmail.com> (raw)
In-Reply-To: <20180212074851.3515-1-go.wigust@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]

Leo Famulari <leo@famulari.name> writes:

> On Wed, Feb 14, 2018 at 04:14:15PM +0300, Oleg Pykhalov wrote:
>> Leo Famulari <leo@famulari.name> writes:
>> > This commit corresponds to the upstream tag "0.1.0", so you can omit the
>> > commit and revision variables, and just set the version to "0.1.0"...
>> 
>> Maybe it's better to get a source via url-fetch from GitHub archive
>> tarball?
>
> Yeah, if the result is the same I think it's better to use url-fetch.

OK.

>> > I think you could use the patch-shebang procedure from (guix build
>> > utils), as in the package for woof.
>> 
>> As I see only for Perl, because folling does nothing:
>> --8<---------------cut here---------------start------------->8---
>> (patch-shebang "epipe"
>>   (list (string-append (assoc-ref %build-inputs "bash")
>>                        "/bin")))
>> --8<---------------cut here---------------end--------------->8---
>
> Huh, weird! Well, I think that whatever works should be fine.

Pushed as 5b2382929959db9d883982329ec8fdf4103a9351

I'll close the bug report.

Oleg.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2018-02-15 17:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12  7:48 [bug#30433] [PATCH] gnu: Add epipe Oleg Pykhalov
2018-02-12 19:38 ` Leo Famulari
2018-02-14 13:14   ` Oleg Pykhalov
2018-02-14 20:51     ` Leo Famulari
2018-02-15 17:47       ` Oleg Pykhalov [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a7waxhzf.fsf@gmail.com \
    --to=go.wigust@gmail.com \
    --cc=30433-done@debbugs.gnu.org \
    --cc=30433@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.