all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, Alex Kost <alezost@gmail.com>
Subject: Re: Problems with downloading from https
Date: Mon, 27 Oct 2014 17:24:14 +0100	[thread overview]
Message-ID: <87y4s1zdjl.fsf@gnu.org> (raw)
In-Reply-To: <87fve9po7v.fsf@yeeloong.lan> (Mark H. Weaver's message of "Mon, 27 Oct 2014 10:43:48 -0400")

Mark H Weaver <mhw@netris.org> skribis:

> Alex Kost <alezost@gmail.com> writes:
>
>> Why not just allow gnutls and other packages to install guile modules in
>> a site dir (without version) and to augment GUILE_LOAD_PATH with it as I
>> suggested at
>> <http://lists.gnu.org/archive/html/guix-devel/2014-10/msg00333.html>?
>
> In my opinion, this is the right fix.  There is plenty of Guile code
> that works on both Guile 1.8 and Guile 2.0, so there's no need to put
> Scheme modules in versioned directories.  We provide 'cond-expand' when
> it's really needed, after all.

A problem is that it would make it impossible to install the 1.8/2.1 and
the 2.0 version of something in the same profile.

Currently it’s possible to install both ‘python’ and ‘python2’ in the
same profile, as well as ‘python-foo’ and ‘python2-foo’.

With the addition of a --program-suffix configure flag, it would be
possible to do the same with Guile 1.8/2.0/2.1.

I think it’s a useful feature.  WDYT?

> Furthermore, if changing the installation directory of the GnuTLS
> modules broke Guix, there's a non-trivial possibility that we might
> break something else.

Given that the search path spec for guile-2.0 has always been site/2.0,
I think this change is unlikely to break anything else.  On the
contrary: this change brought GnuTLS in conformance with the other
Guile-using packages.

Thanks,
Ludo’.

  reply	other threads:[~2014-10-27 16:24 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-25 17:30 Problems with downloading from https Alex Kost
2014-10-25 20:02 ` Ian Denhardt
2014-10-26  7:03   ` Alex Kost
2014-10-26 13:46     ` Ludovic Courtès
2014-10-26 19:35       ` Alex Kost
2014-10-26 21:01         ` Ludovic Courtès
2014-10-27  9:06           ` Mark H Weaver
2014-10-27 12:24             ` Ludovic Courtès
2014-10-27 12:44               ` Ludovic Courtès
2014-10-27 13:27               ` Alex Kost
2014-10-27 14:43                 ` Mark H Weaver
2014-10-27 16:24                   ` Ludovic Courtès [this message]
2014-10-27 16:44                     ` Alex Kost
2014-10-28  8:03                       ` Ludovic Courtès
2014-10-29 22:22                         ` Andreas Enge
2014-10-30  7:27                           ` Alex Kost
2014-10-30  7:49                             ` Andreas Enge
2014-10-30 12:31                               ` Alex Kost
2014-10-30 12:38                                 ` Andreas Enge
2014-10-30 19:30                                   ` Alex Kost
2014-10-30 23:07                                   ` Different versions of a package in the same profile? Ludovic Courtès
2014-11-01 10:46                                     ` Andreas Enge
2014-11-02 17:22                                       ` Ludovic Courtès
2014-11-02 17:39                                         ` Andreas Enge
2014-10-30 13:20                             ` Problems with downloading from https Ludovic Courtès
2014-10-30 17:05                             ` Ian Denhardt
2014-10-30 19:08                               ` Alex Kost
2014-10-31  4:54                                 ` Ian Denhardt
2014-10-30 14:48               ` Ludovic Courtès
2014-10-27 13:01             ` Alex Kost
2014-10-27 14:32               ` Mark H Weaver
2014-10-25 21:53 ` Ludovic Courtès
2014-10-26  5:30   ` [PATCH 0/1] " Ian Denhardt
2014-10-26  5:21     ` [PATCH 1/1] README: add a note about optional GnuTLS dependency Ian Denhardt
2014-10-27 12:54       ` Ludovic Courtès
2014-10-27 10:49     ` [PATCH 0/1] Re: Problems with downloading from https Ian Denhardt

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y4s1zdjl.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.