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

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.
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?

Greetings,
janneke

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

  reply	other threads:[~2020-04-13  7:12 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 [this message]
2020-04-13 10:44     ` Ludovic Courtès

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=87tv1nc11n.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=40581@debbugs.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.