unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Chris Vine <vine35792468@gmail.com>
To: Guile User <guile-user@gnu.org>
Subject: Re: Guile 3.0.7 compile cache messages
Date: Thu, 3 Jun 2021 00:09:16 +0100	[thread overview]
Message-ID: <20210603000916.885d72494c3636bb5ff1bfdb@gmail.com> (raw)
In-Reply-To: <ee5ea46f-29ab-c1ee-e3dd-f88826596f66@posteo.de>

On Wed,  2 Jun 2021 21:52:15 +0000
Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> wrote:
[snip]
> I think the assumption is that I was installing my project in any way. However,
> I am merely running its Guile code, without installing it anywhere in Guix or my
> system.

I still think you may be misunderstanding what I and/or others have
said.

If bytecode files are installed in site-ccache then you have "installed
your project".  From your README, maybe your running of 'bash
guix-env/env.sh' has done that.  As I have said, I do not use guix so I
can't say for sure.  As I also said, it cannot be the case that "I am
merely running its Guile code, without installing it anywhere in Guix
or my system", because guile will not install any files in site-ccache
upon auto-compiling.

Anyway, this has gone far enough and I think the various responses you
have received have explained the problem: it is up to you how you take
it forward as you will.  You have reported elsewhere that you have
deleted the files in site-ccache (in other words, undone the
"installation"), which obviously will stop the warnings and is one of
the approaches I recommended.  You will have to make sure they aren't
"installed" again (and note that your bytecode files in local cache are
no longer managed by guix).

Let's leave it there.



  reply	other threads:[~2021-06-02 23:09 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 [this message]
2021-06-02 20:51           ` Adriano Peluso
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=20210603000916.885d72494c3636bb5ff1bfdb@gmail.com \
    --to=vine35792468@gmail.com \
    --cc=guile-user@gnu.org \
    /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).