From: Leo Famulari <leo@famulari.name>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 30433@debbugs.gnu.org
Subject: [bug#30433] [PATCH] gnu: Add epipe.
Date: Wed, 14 Feb 2018 15:51:44 -0500 [thread overview]
Message-ID: <20180214205144.GB18223@jasmine.lan> (raw)
In-Reply-To: <874lmjiuhk.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 921 bytes --]
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.
> > 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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-14 20:52 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 [this message]
2018-02-15 17:47 ` Oleg Pykhalov
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=20180214205144.GB18223@jasmine.lan \
--to=leo@famulari.name \
--cc=30433@debbugs.gnu.org \
--cc=go.wigust@gmail.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).