unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: guile: Add "site-ccache" to the search path.
Date: Wed, 29 Jun 2016 15:14:42 +0200	[thread overview]
Message-ID: <87inws87ct.fsf@gnu.org> (raw)
In-Reply-To: <87por0fmkl.fsf@gmail.com> (Alex Kost's message of "Wed, 29 Jun 2016 11:04:10 +0300")

Alex Kost <alezost@gmail.com> skribis:

> Add "site-ccache" since it's a directory where .go files of guile
> packages should go (for example, 'guile-ssh' installs *.go there).

Indeed.

> I suppose this patch should go to 'core-updates-next', right?

Yes.

> From 489a54be23753f61fa9c3a318d411eb48fb75bf6 Mon Sep 17 00:00:00 2001
> From: Alex Kost <alezost@gmail.com>
> Date: Wed, 29 Jun 2016 10:51:26 +0300
> Subject: [PATCH] gnu: guile: Add "site-ccache" to the search path.
>
> * gnu/packages/guile.scm (guile-2.0)[native-search-paths]: Add
> "lib/guile/2.0/site-ccache" to GUILE_LOAD_COMPILED_PATH.
> (guile-next): Likewise.

[...]

> --- a/gnu/packages/guile.scm
> +++ b/gnu/packages/guile.scm
> @@ -180,6 +180,7 @@ without requiring the source code to be rewritten.")
>            (search-path-specification
>             (variable "GUILE_LOAD_COMPILED_PATH")
>             (files '("lib/guile/2.0/ccache"
> +                    "lib/guile/2.0/site-ccache"
>                      "share/guile/site/2.0")))))

I wonder if it makes sense to keep lib/guile/2.0/ccache since that is
(meant to be) used exclusively by Guile itself, I think.

Andy, WDYT?

Thanks,
Ludo’.

  reply	other threads:[~2016-06-29 13:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29  8:04 [PATCH] gnu: guile: Add "site-ccache" to the search path Alex Kost
2016-06-29 13:14 ` Ludovic Courtès [this message]
2016-06-29 14:00   ` Andy Wingo
2016-06-30 10:31     ` Ludovic Courtès
2016-06-30 14:18       ` Alex Kost
2016-06-30 21:14         ` Ludovic Courtès

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=87inws87ct.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --cc=guix-devel@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.
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).