unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: guile: Add "site-ccache" to the search path.
Date: Thu, 30 Jun 2016 17:18:44 +0300	[thread overview]
Message-ID: <87twgaahff.fsf@gmail.com> (raw)
In-Reply-To: <87inwr55on.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 30 Jun 2016 12:31:20 +0200")

Ludovic Courtès (2016-06-30 13:31 +0300) wrote:

> Andy Wingo <wingo@igalia.com> skribis:
>
>> On Wed 29 Jun 2016 15:14, ludo@gnu.org (Ludovic Courtès) writes:
>>
>>>> --- 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?
>>
>> Removing Guile's own compiled paths from GUILE_LOAD_COMPILED_PATH sounds
>> like a good idea to me, since these are implicitly included via
>> GUILE_SYSTEM_COMPILED_PATH or whatever that is.
>
> OK.  Alex, could you update the patch to not only add 2.x/site-ccache,
> but also remove 2.x/ccache?

Done, committed to 'core-updates-next' as a08539dd1f.

... or did you mean to *send* the updated patch at first?  oops :-)

-- 
Alex

  reply	other threads:[~2016-06-30 14:18 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
2016-06-29 14:00   ` Andy Wingo
2016-06-30 10:31     ` Ludovic Courtès
2016-06-30 14:18       ` Alex Kost [this message]
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=87twgaahff.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).