From: swedebugia <swedebugia@riseup.net>
To: Julien Lepiller <julien@lepiller.eu>,
"33957@debbugs.gnu.org" <33957@debbugs.gnu.org>
Subject: [bug#33957] [PATCH] gnu: Add missing search-path definitions to guile libraries.
Date: Thu, 3 Jan 2019 17:29:41 +0100 [thread overview]
Message-ID: <7cd4b568-f7e3-907f-6a49-7c537cb85c59@riseup.net> (raw)
In-Reply-To: <074DA530-7004-4EED-970C-F8563105C163@lepiller.eu>
On 2019-01-03 08:43, Julien Lepiller wrote:
> Le 3 janvier 2019 01:59:00 GMT+03:00, swedebugia <swedebugia@riseup.net> a écrit :
>> I added missing search-path definitions for guile 2.2.
>
> Hi,
>
> I don't think this is needed. As long as you install guile and its libraries in the same profile, guix will tell you what to do with the search-path.
>
> I'm afraid it'll break on packages that use a different guile as they are defined from the guile2.2 definition.
I don't agree. We simply update the paths when we update guile.
>
> What are you trying to fix exactly?
>
In parabola. When I have guile from parabola installed and install
guile-x and guile-y libraries from guix it does not inform about
search-paths.
Neither does the output of guix package --search-paths.
Maybe we should write a section in the manual about why we choose to not
include these search-paths if that is the outcome.
Thoughts?
--
Cheers Swedebugia
next prev parent reply other threads:[~2019-01-03 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 22:59 [bug#33957] [PATCH] gnu: Add missing search-path definitions to guile libraries swedebugia
2019-01-03 7:43 ` Julien Lepiller
2019-01-03 16:29 ` swedebugia [this message]
2019-01-12 13:46 ` bug#33957: " 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=7cd4b568-f7e3-907f-6a49-7c537cb85c59@riseup.net \
--to=swedebugia@riseup.net \
--cc=33957@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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).