unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: 72766@debbugs.gnu.org
Subject: [bug#72766] [PATCH v3 2/2] gnu: slurm: Move client executables into separate output.
Date: Thu, 24 Oct 2024 15:50:10 +0100	[thread overview]
Message-ID: <875xpha731.fsf@systemreboot.net> (raw)
In-Reply-To: <87plnp251n.fsf@inria.fr>


Hi Ludo,

> I think “bin” would be a more conventional name for the output; this is
> used in a couple of packages and recognized by ‘package->recutils’.

Sure, fixed now.

> However, what does ‘guix size slurm:client’ report?  I suspect it
> depends on slurm:out, in which case moving to a separate output makes no
> difference from that perspective.

Yep, that's right.

$ ./pre-inst-env guix size slurm:out | tail -n1
total: 192.6 MiB
$ ./pre-inst-env guix size slurm:bin | tail -n1
total: 201.3 MiB
$ ./pre-inst-env guix size slurm:bin | grep slurm
/gnu/store/2qhgkq79ahw64n4kmr3znl8v66z0n87j-slurm-23.11.10         192.6    17.5   8.7%
/gnu/store/6f3d93i0zdr48v6bp471dfsk7r89xdqh-slurm-23.11.10-bin     201.3     1.3   0.6%

Should I then go back to the idea of creating a slurm-minimal variant?

Regards,
Arun




  reply	other threads:[~2024-10-24 14:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22 23:30 [bug#72766] [PATCH 0/2] slurm: Enable REST API Arun Isaac
2024-08-22 23:36 ` [bug#72766] [PATCH 1/2] gnu: Add libjwt Arun Isaac
2024-08-22 23:36 ` [bug#72766] [PATCH 2/2] gnu: slurm: Enable REST API Arun Isaac
2024-09-02  7:43   ` Ludovic Courtès
2024-09-06 16:03     ` Arun Isaac
2024-09-06 16:06       ` Arun Isaac
2024-09-09  7:13         ` Ludovic Courtès
2024-09-09 14:59           ` Arun Isaac
2024-09-10  8:32       ` Ludovic Courtès
2024-09-09 15:24 ` [bug#72766] [PATCH v2 1/2] gnu: Add libjwt Arun Isaac
2024-09-09 15:24   ` [bug#72766] [PATCH v2 2/2] gnu: slurm: Enable REST API Arun Isaac
2024-09-10  6:50     ` Ludovic Courtès
2024-09-10 15:02       ` Arun Isaac
2024-09-12  8:24         ` Ludovic Courtès
2024-09-12 11:51           ` Arun Isaac
2024-09-12 15:31             ` Ludovic Courtès
2024-09-16 21:55               ` Arun Isaac
2024-09-17  6:37                 ` Ludovic Courtès
2024-09-17 14:54                   ` Arun Isaac
2024-10-18 14:58 ` [bug#72766] [PATCH v3 0/2] " Arun Isaac
2024-10-18 14:58   ` [bug#72766] [PATCH v3 1/2] gnu: " Arun Isaac
2024-10-18 14:58   ` [bug#72766] [PATCH v3 2/2] gnu: slurm: Move client executables into separate output Arun Isaac
2024-10-24 10:01     ` Ludovic Courtès
2024-10-24 14:50       ` Arun Isaac [this message]
2024-10-25  9:32         ` Ludovic Courtès
2024-10-25 15:23           ` Arun Isaac
2024-10-25 15:24 ` [bug#72766] [PATCH v4] gnu: slurm: Enable REST API Arun Isaac
2024-11-12 10:35   ` 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=875xpha731.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=72766@debbugs.gnu.org \
    --cc=ludovic.courtes@inria.fr \
    /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).