From: Maxime Devos <maximedevos@telenet.be>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Removing #:skip-build? from the crate importer?
Date: Thu, 31 Mar 2022 21:14:09 +0200 [thread overview]
Message-ID: <0fcc64bf008af471370e6704bffeb3c0174861be.camel@telenet.be> (raw)
In-Reply-To: <d4b30b4a12b09300da1f59ff4c25c73263bee4ba.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
Liliana Marie Prikler schreef op do 31-03-2022 om 21:07 [+0200]:
> Hi Maxime,
>
> similar discussions have been had in the past, but thanks for raising
> them again. As far as I'm aware, the "consensus" – if it can be called
> such – is that due to Rust packages often being a giant nothing burger
> both in terms of what they actually do and in what can be used for
> subsequent builds, but still generating a lot of hot air literally when
> evaluated on CI, we ought to skip the build in intermediate packages.
I was not aware that it has been discussed in the past ,thanks.
> There are a few counter-proposals. One suggestion that has been
> raised, but not yet implemented, would be to make it so that build
> results can actually be reused. This is the most promising
> conceptually, but from what I can gather from those working on it might
> not be that easy to pull off.
Yes, that would be nice. Are there already some concrete patches that
can be tested? I know there are some (ideas for?) patches to move
development-inputs->native-inputs but I don't think I've seen any
patches for actually reusing build results yet ...
Greetings,
Maxime
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-03-31 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 19:07 Removing #:skip-build? from the crate importer? Liliana Marie Prikler
2022-03-31 19:14 ` Maxime Devos [this message]
2022-04-02 9:45 ` Hartmut Goebel
2022-04-02 10:53 ` Maxime Devos
-- strict thread matches above, loose matches on Subject: below --
2022-03-31 11:55 Maxime Devos
2022-03-31 19:47 ` Hartmut Goebel
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0fcc64bf008af471370e6704bffeb3c0174861be.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.