From: jgart via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 51494@debbugs.gnu.org
Cc: rprior@protonmail.com
Subject: bug#51494: guix shell make --rebuild-cache on manifest change
Date: Fri, 29 Oct 2021 17:30:31 -0400 [thread overview]
Message-ID: <20211029173031.GB21467@gac.attlocal.net> (raw)
10/29/2021 | 05:18:17 PM jgart: civodul, wdyt of `--rebuild-cache` being automatic/the default for guix shell instead of having to explicitly specify the flag to rebuild the cache?
10/29/2021 | 05:18:31 PM jgart: I think this is the default for docker or how docker works
10/29/2021 | 05:18:42 PM jgart: I was discussing this with Ryan Prior the other day
10/29/2021 | 05:18:45 PM nckx: Doesn't that defeat the purpose?
10/29/2021 | 05:18:51 PM jgart: who had mentioned it to me
10/29/2021 | 05:19:36 PM jgart: If you change the manifest then guix shell should rebuild the cache
10/29/2021 | 05:19:40 PM jgart: that's how it works for docker
10/29/2021 | 05:19:53 PM jgart: > Create manifest with 2 packages: python, python-requests. Run guix shell. Decide you want python-lxml instead: exit shell, edit manifest to add python-lxml, re-run guix shell. Type import lxml, it says no module named lxml.
10/29/2021 | 05:20:05 PM jgart: That's quoting Ryan from our conversation
10/29/2021 | 05:20:11 PM nckx: Oh.
10/29/2021 | 05:20:19 PM nckx: That just sounds like a bug?
10/29/2021 | 05:20:27 PM jgart: That was his experience that he was frustrated with
10/29/2021 | 05:20:30 PM jgart: yup
next reply other threads:[~2021-10-29 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 21:30 jgart via Bug reports for GNU Guix [this message]
2021-10-29 23:08 ` bug#51494: guix shell make --rebuild-cache on manifest change Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-10-30 0:10 ` jgart via Bug reports for GNU Guix
2021-10-30 0:35 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
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=20211029173031.GB21467@gac.attlocal.net \
--to=bug-guix@gnu.org \
--cc=51494@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=rprior@protonmail.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).