all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Thompson <dthompson2@worcester.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add wireless-tools.
Date: Sat, 19 Jul 2014 08:47:03 -0400	[thread overview]
Message-ID: <87y4vpqzw8.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <874mydilcs.fsf@gnu.org>

Ludovic Courtès <ludo@gnu.org> writes:

> David Thompson <dthompson2@worcester.edu> skribis:
>
>> There was a conversation on #guix today about wpa-supplicant possibly
>> needing wireless tools in order to work.  Well, I haven't tested that
>> yet, but I did write a package for the wireless tools.
>
> I think it expects it to be in $PATH.

So I guess we can either try to patch the source code to explicitly
refer to the wireless-tools in the store, or make wireless-tools a
propagated input?

>> From 03ec990504a3f96385587eb1cf4396cab3332617 Mon Sep 17 00:00:00 2001
>> From: David Thompson <dthompson2@worcester.edu>
>> Date: Fri, 18 Jul 2014 21:23:58 -0400
>> Subject: [PATCH] gnu: Add wireless-tools.
>>
>> * gnu/packages/linux.scm (wireless-tools): New variable.
>
> Excellent, please push.

Pushed!

> I think we should add to the installation image, no?

That's a good idea.  Add to %base-packages?

-- 
David Thompson
Web Developer - Free Software Foundation - http://fsf.org
GPG Key: 0FF1D807
Support the FSF: https://fsf.org/donate

  reply	other threads:[~2014-07-19 12:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-19  1:28 [PATCH] gnu: Add wireless-tools David Thompson
2014-07-19  1:30 ` David Thompson
2014-07-19 12:28 ` Ludovic Courtès
2014-07-19 12:47   ` David Thompson [this message]
2014-07-19 13:18     ` Ludovic Courtès
2014-07-19 13:41       ` David Thompson

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=87y4vpqzw8.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me \
    --to=dthompson2@worcester.edu \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 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.