unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: lm-sensors vanished
Date: Sat, 16 Jul 2016 15:13:26 +0200	[thread overview]
Message-ID: <87a8hhafpl.fsf@gnu.org> (raw)
In-Reply-To: <20160715163418.GA3598@solar> (Andreas Enge's message of "Fri, 15 Jul 2016 18:34:18 +0200")

Andreas Enge <andreas@enge.fr> skribis:

> More on lm-sensors, which we will probably need for installing the hydra
> replacement: First, the input rrdtool is not referenced in the output; could
> it be moved to native-inputs, or maybe even dropped? I tried a compilation
> without it, and it succeeded, but I did not yet check whether the result
> actually works.

To make sure, I’d suggest grepping the source of lm-sensors for any
mention of rrdtool.  It might be safe to remove it.

> Second, it is extraordinarily big, which means we cannot reasonably add it
> to the installation image, and then it will take a long time to download
> during the installation:
> $ guix size lm-sensors
> /gnu/store/35655d6dqw80ziqwxn6yhszqmyknxy39-lm-sensors-3.3.5       413.2     0.5   0.1%

[...]

> /gnu/store/sjvcirri2bg7q5hlrkaywhmxllik0cfx-gcc-4.9.3              138.2    77.2  18.7%

Keep in mind that most of it is due to <http://bugs.gnu.org/23077>,
fixed in core-updates.

> Perl is needed for two scripts:
> bin/sensors-conf-convert, which
> "Convert[s] a sensors.conf file from the old (Linux 2.4, lm-sensors 2)
> symbol names to the new (Linux 2.6 or 3, lm-sensors 3) symbol names."
> and which is probably not important for GuixSD.
> And sbin/sensors-detect, which I think is needed.

OK.

> Could we maybe drop gnuplot, which seems to pull in a lot of X related
> packages?

We’d need to check what it’s used for, but maybe yes.

Thanks,
Ludo’.

  reply	other threads:[~2016-07-16 13:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15 15:40 lm-sensors vanished Andreas Enge
2016-07-15 16:11 ` Leo Famulari
2016-07-15 16:16   ` Leo Famulari
2016-07-15 16:23     ` Andreas Enge
2016-07-15 17:24   ` Andreas Enge
2016-07-15 16:34 ` Andreas Enge
2016-07-16 13:13   ` Ludovic Courtès [this message]
2016-07-16 13:32     ` Andreas Enge
2016-07-17 13:20       ` 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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a8hhafpl.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andreas@enge.fr \
    --cc=guix-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).