all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: Rene <pacoon@protonmail.com>, 40581@debbugs.gnu.org
Subject: bug#40581: [wip-hurd-vm] uptime from coreutils looks for /bin/w
Date: Mon, 13 Apr 2020 12:44:35 +0200	[thread overview]
Message-ID: <877dyjmzqk.fsf@gnu.org> (raw)
In-Reply-To: <87tv1nc11n.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Mon, 13 Apr 2020 09:11:48 +0200")

Hey ho!

Jan Nieuwenhuizen <janneke@gnu.org> skribis:

> Rene writes:
>
> Hello Rene, Efraim,
>
>> Debian project currently uses `/bin/w` from the hurd package, so I
>> propose the attached patch.
>
> LGTM!
>
>> @@ -398,6 +399,9 @@ boot, since this cannot be done from GNU/Linux."
>>                 (substitute* '("startup/startup.c" "init/init.c" "config/ttys")
>>                   (("/libexec/")
>>                    (string-append out "/libexec/")))
>> +               (substitute* '("utils/uptime.sh")
>> +                 (("/bin/w")
>> +                  (string-append out "/bin/w")))
>>                 (substitute* "daemons/console-run.c"
>>                   (("/hurd/")
>>                    (string-append out "/hurd/")))
>
> Looking at this again it looks fine; following the pattern we created.

Yup, LGTM!

> This now makes me wonder whether upstream Hurd could use a patch for
> ${bindir} and ${libexecdir}.  Possibly even for `/hurd'.
>
> What do you all think?

Yes, I think this prefix issue should be fixed upstream.

Ludo’.

      reply	other threads:[~2020-04-13 10:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-12 18:30 bug#40581: [wip-hurd-vm] uptime from coreutils looks for /bin/w Efraim Flashner
2020-04-13  3:54 ` Rene via Bug reports for GNU Guix
2020-04-13  7:11   ` Jan Nieuwenhuizen
2020-04-13 10:44     ` Ludovic Courtès [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=877dyjmzqk.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=40581@debbugs.gnu.org \
    --cc=janneke@gnu.org \
    --cc=pacoon@protonmail.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.