From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: 66647@debbugs.gnu.org
Subject: bug#66647: Installation of RPMs produced by ‘guix pack’ is super slow
Date: Fri, 20 Oct 2023 11:33:08 -0400 [thread overview]
Message-ID: <87jzrhia17.fsf@gmail.com> (raw)
In-Reply-To: <87a5sdvblv.fsf@inria.fr> ("Ludovic Courtès"'s message of "Fri, 20 Oct 2023 12:20:44 +0200")
Hi!
Ludovic Courtès <ludovic.courtes@inria.fr> writes:
> Hello!
>
> I made friends at work when I told them we could provide an RPM for any
> modern package to install on their old RPM-based distro. :-)
>
> However, installing those RPMs takes a lot of time. For example,
> installing the RPM for ‘gmsh’ (closure: 596 MiB; thousands of files)
> takes ~45mn.
>
> Is there something about the metadata generated by (guix rpm) that could
> be improved, or are we hitting some limitation of the RPM format or
> implementation?
What? That's crazy. I haven't experimented with it recently, but I
used to generate packages for Jami back when it had a closure of 2 GiB
and it took many seconds, but not that much.
Many RPM is doing extra checks now?
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-10-20 16:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 10:20 bug#66647: Installation of RPMs produced by ‘guix pack’ is super slow Ludovic Courtès
2023-10-20 15:33 ` Maxim Cournoyer [this message]
2023-10-20 15:34 ` Maxim Cournoyer
2023-10-22 21:57 ` Ludovic Courtès
2023-10-23 1:35 ` Maxim Cournoyer
2023-10-23 12:16 ` Simon Tournier
2023-10-23 14:37 ` Maxim Cournoyer
2023-11-13 12:31 ` Loïc SIRVIN
2023-11-14 11:49 ` Simon Tournier
2023-11-25 14:22 ` Ludovic Courtès
2023-11-28 13:31 ` Simon Tournier
2023-12-02 23:13 ` Maxim Cournoyer
2024-01-11 16:57 ` Simon Tournier
2024-01-15 3:43 ` Maxim Cournoyer
2024-01-15 9:12 ` Ludovic Courtès
2024-01-17 15:21 ` Simon Tournier
2024-01-17 22:21 ` Maxim Cournoyer
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=87jzrhia17.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=66647@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).