From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Mikael Djurfeldt <mikael@djurfeldt.com>
Cc: guix-devel@gnu.org, guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] Append effective version to GUILE_LOAD[_COMPILED]_PATH
Date: Sat, 19 Mar 2016 10:26:08 +0100 [thread overview]
Message-ID: <874mc2yg27.fsf@drakenvlieg.flower> (raw)
In-Reply-To: <CAA2XvwLt2GzBoMNRv-0yGoYKW_9SP07G=Ayb4VGx9W1av4xpyA@mail.gmail.com> (Mikael Djurfeldt's message of "Wed, 16 Mar 2016 15:19:26 +0100")
Mikael Djurfeldt writes:
> In python, the version number is higher up in the directory hierarchy,
> which, hypothetically, allows newer versions to have "inventions" in
> the more detailed directory structure:
>
> /usr/lib/python2.6
> /usr/lib/python2.7
> etc
>
> Just a thought.
Python's case is a bit different
* Python does not look at any environment variable to boot
in contrast, setting GUILE_LOAD_*PATH to the wrong place makes Guile
barf trying to load eval.* or boot-9.*. Also, guix by default sets
GUILE_LOAD_PATH and GUILE_LOAD_COMPILED_PATH, thus "ensuring" that
different guile major versions will fail to boot.
Do we want Guile to look at environment variables to find its core
libraries?
* Python has magic numbers and skip/recompiles if a .py[oc] does
not match
This resembles what Ludovic suggested and what I have submitted a patch
for, to skip invalid .go files.
Greetings, Jan
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
next prev parent reply other threads:[~2016-03-19 9:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 13:13 [PATCH] Append effective version to GUILE_LOAD[_COMPILED]_PATH Jan Nieuwenhuizen
2016-03-11 18:14 ` [PATCH] Skip invalid compiled file found, continue searching path Jan Nieuwenhuizen
2016-03-11 22:02 ` David Kastrup
2016-03-13 10:15 ` Jan Nieuwenhuizen
2016-03-13 11:05 ` David Kastrup
2016-03-13 11:10 ` David Kastrup
2016-03-13 10:03 ` [PATCH v3] " Jan Nieuwenhuizen
2016-03-13 10:19 ` Jan Nieuwenhuizen
2016-03-14 16:10 ` [PATCH v4] " Jan Nieuwenhuizen
2016-03-16 14:19 ` [PATCH] Append effective version to GUILE_LOAD[_COMPILED]_PATH Mikael Djurfeldt
2016-03-19 9:26 ` Jan Nieuwenhuizen [this message]
2016-03-19 21:09 ` 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://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=874mc2yg27.fsf@drakenvlieg.flower \
--to=janneke@gnu.org \
--cc=guile-devel@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mikael@djurfeldt.com \
/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).