GNU bug report logs - #41735
[PATCH 0/2] Remove X libraries from bare-bones system closure.

Previous Next

Full log

Message #14 received at 41735 <at> debbugs.gnu.org (full text, mbox):

From: Jan Nieuwenhuizen <janneke <at> gnu.org>
To: Mathieu Othacehe <m.othacehe <at> gmail.com>
Cc: Mathieu Othacehe <othacehe <at> gnu.org>, 41735 <at> debbugs.gnu.org
Subject: Re: [bug#41735] [PATCH 1/2] gnu: Add openssh-no-x.
Date: Sat, 06 Jun 2020 12:00:46 +0200

Mathieu Othacehe writes:

Hello!

> * gnu/packages/ssh.scm (openssh-no-x): New variable.
[..]
> diff --git a/gnu/packages/ssh.scm b/gnu/packages/ssh.scm
[..]
> +;; OpenSSH without X support. This allows to use OpenSSH without dragging X
> +;; libraries to the closure.
> +(define-public openssh-no-x
> +  (package
> +    (inherit openssh)
> +    (name "openssh-no-x")
> +    (inputs (alist-delete "xauth" (package-inputs openssh)))))

I like it!  Maybe use -sans-x?

Two remarks: after merging, we may want to use openssh-no-x for the Hurd
too and drop this from openssh proper:

             ,@(if (hurd-target?)
                   '()
                   `(("xauth" ,xauth)))))         ; for 'ssh -X' and 'ssh -Y'

We have this bit because xauth does not compile for the Hurd yet,
but it's kind of a kludge.

Not to hold this up and maybe we should take this discussion
elsewhere...but I have a ~5y old, bit-rotting stack of LilyPond cross
build packages (foo-SANS-X) laying around.  At the time--much to my
suprise--I found the LilyPond community less than enthousiastic to move
their binary package builds to Guix (yet); but adding these -NO-X
packages felt a bit weird.  So, I wonder if we could address the X'yness
of packages in a more structured way, that would be nice...

Greetings,
Janneke

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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.