all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 26770@debbugs.gnu.org
Subject: bug#26770: [PATCH] gnu: tailon: Add missing inputs.
Date: Mon, 15 May 2017 07:25:49 +0100	[thread overview]
Message-ID: <20170515072549.5c933ddc@cbaines.net> (raw)
In-Reply-To: <877f1v1cwq.fsf@fastmail.com>

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

On Fri, 05 May 2017 18:33:41 +0200
Marius Bakke <mbakke@fastmail.com> wrote:

> Christopher Baines <mail@cbaines.net> writes:
> 
> > * gnu/packages/logging.scm (tailon)[inputs]: Add grep, gawk, sed
> > and coreutils as inputs.
> >   [arguments]: Wrap bin/tailon to include some inputs in the PATH.  
> 
> Generally it's better to fully qualify the paths to these programs in
> the code. Is that difficult here?

Good point, I've send an updated patch that does this.

> I think all of these inputs are already available, so you can do e.g.:
> (substitute "foo"
>   (("'grep'") (which "grep))
>   (("'gawk'") (which "gawk")))
> 
> ...instead of referencing the inputs explicitly.

That works, I've changed that in the latest patch also.

Thanks for your review :)

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

  reply	other threads:[~2017-05-15  6:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04  6:47 bug#26770: [PATCH] gnu: tailon: Add missing inputs Christopher Baines
2017-05-05 16:33 ` Marius Bakke
2017-05-15  6:25   ` Christopher Baines [this message]
2017-05-15  6:11 ` bug#26770: [PATCH] gnu: tailon: Use absolute paths for commands Christopher Baines
2017-05-15 15:59   ` Marius Bakke
2017-05-16 19:49     ` Christopher Baines
2017-05-17 14:53       ` Marius Bakke
2017-05-18 18:50         ` Christopher Baines
2017-05-16 19:40 ` Christopher Baines

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=20170515072549.5c933ddc@cbaines.net \
    --to=mail@cbaines.net \
    --cc=26770@debbugs.gnu.org \
    --cc=mbakke@fastmail.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 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.