From: Leo Famulari <leo@famulari.name>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Examples on why ungrafting is necessary
Date: Sun, 14 Mar 2021 16:43:39 -0400 [thread overview]
Message-ID: <YE51e8CPhmkb6YjE@jasmine.lan> (raw)
In-Reply-To: <86wnud6db3.fsf@gmail.com>
On Thu, Mar 11, 2021 at 02:16:16PM +0100, zimoun wrote:
> Updating the package r-chemminer, it leads to this huge stack of
> grafts. To be concrete, it is 84 grafts for a “simple” R packages. On
> my machine, the grafting steps are longer than building (compiling and R
> dance).
The performance of grafting largely corresponds to I/O speed.
> We definitively need a way to tackle this. Maybe when is in frozen
> state, we could spend 2-5 days to tackle as much as graft that we can.
>
> The previous Leo’s initiative is really worth and maybe we should have a
> hackathon or something because my feeling is that more grafts are added
> than removed.
To clarify: the number of grafts added is exactly the same number of
grafts that are removed. But, it takes longer to remove them, because
ungrafted requires us to recompile every affected package.
prev parent reply other threads:[~2021-03-14 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 13:16 Examples on why ungrafting is necessary zimoun
2021-03-14 15:49 ` Joshua Branson
2021-03-14 20:43 ` Leo Famulari [this message]
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=YE51e8CPhmkb6YjE@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.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 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).