From: Adriano Peluso <randomlooser@riseup.net>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>,
Chris Vine <vine35792468@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Guile 3.0.7 compile cache messages
Date: Wed, 02 Jun 2021 22:51:56 +0200 [thread overview]
Message-ID: <b77b7ba4aed1da7e949be2c1883af3577df1ec69.camel@riseup.net> (raw)
In-Reply-To: <b37bb878-f954-4fa1-2815-e0bb348ebd41@posteo.de>
Il giorno mer, 02/06/2021 alle 12.20 +0000, Zelphir Kaltstahl ha
scritto:
> > > >
>
> How do I go about it? Simply removing the cache folder the messages
> point to?
>
> And what commands would that alternative workflow entail?
I skimmed your project and I see that there's only one dependency:
Guile
In fact, being the needs of your project so minimal, using a Guix
environment is a bit of an overkill
The way to deal with developing a project that is distrubuted throug
Guix would be to have and environment (or a profile) based on your
project
In such environment you would have a shell with all your project
dependencies in it BUT your project itself
So you would git checkout your project within such environment and you
could build it, run the tests (if there are any) and generally work
with it in such a shell
as far as I understand (I stil don't know how channels work) you have
installed your project with Guix AND you are working on it
That's why the compiled code is in 2 different places
One of them was installed by Guix and another one has been put there by
Guile when it has autocompiled it
You can
1) cancel the cache in your home folder
2) remove the package installed by Guix (maybe also garbage collect the
store)
3) create a guix environment for your project
The Guix cookbook has a paragraph on the difference between Guix
profiles and Guix environments and also the Guix blog has something
about this
I'd also discuss this on the guix mailing list as people there are more
immediately ready to discuss scenarios involving Guix
Hope this helps
next prev parent reply other threads:[~2021-06-02 20:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 19:46 Guile 3.0.7 compile cache messages Zelphir Kaltstahl
2021-06-01 12:14 ` Olivier Dion via General Guile related discussions
2021-06-02 6:00 ` Adriano Peluso
2021-06-02 8:52 ` Zelphir Kaltstahl
2021-06-02 10:30 ` Chris Vine
2021-06-02 12:20 ` Zelphir Kaltstahl
2021-06-02 12:38 ` Matt Wette
2021-06-02 16:53 ` Chris Vine
2021-06-02 21:52 ` Zelphir Kaltstahl
2021-06-02 23:09 ` Chris Vine
2021-06-02 20:51 ` Adriano Peluso [this message]
2021-06-02 21:45 ` Zelphir Kaltstahl
2021-06-02 22:15 ` Zelphir Kaltstahl
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b77b7ba4aed1da7e949be2c1883af3577df1ec69.camel@riseup.net \
--to=randomlooser@riseup.net \
--cc=guile-user@gnu.org \
--cc=vine35792468@gmail.com \
--cc=zelphirkaltstahl@posteo.de \
/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.
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).