* Re: 01/01: gnu: guile-for-guile-emacs: Use guile-2.0 search paths.
[not found] ` <E1aaH3W-0006Vn-7g@vcs.savannah.gnu.org>
@ 2016-02-29 16:53 ` Mark H Weaver
2016-02-29 17:46 ` Christopher Allan Webber
2016-02-29 20:34 ` Ricardo Wurmus
0 siblings, 2 replies; 3+ messages in thread
From: Mark H Weaver @ 2016-02-29 16:53 UTC (permalink / raw)
To: Ricardo Wurmus; +Cc: guix-devel
Ricardo Wurmus <rekado@elephly.net> writes:
> rekado pushed a commit to branch master
> in repository guix.
>
> commit daeb61f7a92a178b0ac4a5c11b62b962293517e5
> Author: Ricardo Wurmus <rekado@elephly.net>
> Date: Sun Feb 28 20:42:13 2016 +0100
>
> gnu: guile-for-guile-emacs: Use guile-2.0 search paths.
>
> * gnu/packages/guile.scm (guile-for-guile-emacs)[native-search-paths]:
> Use the same search paths as guile-2.0.
I think this is incorrect. guile-for-guile-emacs is not guile-2.0, it
is very close to guile-2.2. What's the rationale for this?
Mark
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 01/01: gnu: guile-for-guile-emacs: Use guile-2.0 search paths.
2016-02-29 16:53 ` 01/01: gnu: guile-for-guile-emacs: Use guile-2.0 search paths Mark H Weaver
@ 2016-02-29 17:46 ` Christopher Allan Webber
2016-02-29 20:34 ` Ricardo Wurmus
1 sibling, 0 replies; 3+ messages in thread
From: Christopher Allan Webber @ 2016-02-29 17:46 UTC (permalink / raw)
To: Mark H Weaver; +Cc: guix-devel
Mark H Weaver writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> rekado pushed a commit to branch master
>> in repository guix.
>>
>> commit daeb61f7a92a178b0ac4a5c11b62b962293517e5
>> Author: Ricardo Wurmus <rekado@elephly.net>
>> Date: Sun Feb 28 20:42:13 2016 +0100
>>
>> gnu: guile-for-guile-emacs: Use guile-2.0 search paths.
>>
>> * gnu/packages/guile.scm (guile-for-guile-emacs)[native-search-paths]:
>> Use the same search paths as guile-2.0.
>
> I think this is incorrect. guile-for-guile-emacs is not guile-2.0, it
> is very close to guile-2.2. What's the rationale for this?
>
> Mark
I'm not sure; guile-for-guile-emacs is about a year out of date from git
master. But I guess even a year ago maybe the search paths should have
been for 2.2?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 01/01: gnu: guile-for-guile-emacs: Use guile-2.0 search paths.
2016-02-29 16:53 ` 01/01: gnu: guile-for-guile-emacs: Use guile-2.0 search paths Mark H Weaver
2016-02-29 17:46 ` Christopher Allan Webber
@ 2016-02-29 20:34 ` Ricardo Wurmus
1 sibling, 0 replies; 3+ messages in thread
From: Ricardo Wurmus @ 2016-02-29 20:34 UTC (permalink / raw)
To: Mark H Weaver; +Cc: guix-devel
Mark H Weaver <mhw@netris.org> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> rekado pushed a commit to branch master
>> in repository guix.
>>
>> commit daeb61f7a92a178b0ac4a5c11b62b962293517e5
>> Author: Ricardo Wurmus <rekado@elephly.net>
>> Date: Sun Feb 28 20:42:13 2016 +0100
>>
>> gnu: guile-for-guile-emacs: Use guile-2.0 search paths.
>>
>> * gnu/packages/guile.scm (guile-for-guile-emacs)[native-search-paths]:
>> Use the same search paths as guile-2.0.
>
> I think this is incorrect. guile-for-guile-emacs is not guile-2.0, it
> is very close to guile-2.2. What's the rationale for this?
This is essentially reverting part of commit dd90ed892a7dbe13a214b2
which broke the build of “guile-for-guile-emacs”. Previously,
“guile-for-guile-emacs” inherited the “guile-2.0” search paths via
“guile-next”.
~~ Ricardo
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-02-29 20:34 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20160229061118.24868.38687@vcs.savannah.gnu.org>
[not found] ` <E1aaH3W-0006Vn-7g@vcs.savannah.gnu.org>
2016-02-29 16:53 ` 01/01: gnu: guile-for-guile-emacs: Use guile-2.0 search paths Mark H Weaver
2016-02-29 17:46 ` Christopher Allan Webber
2016-02-29 20:34 ` Ricardo Wurmus
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).