From: swedebugia <swedebugia@riseup.net>
To: Leo Famulari <leo@famulari.name>,
33261@debbugs.gnu.org, bjoern.hoefling@bjoernhoefling.de
Subject: bug#33261: [substitute-urls] Fails when given only "berlin.guixsd.org"
Date: Mon, 5 Nov 2018 21:48:55 +0100 [thread overview]
Message-ID: <62e5ca73-88e9-7e50-ea0c-f4a8f4c50dbf@riseup.net> (raw)
In-Reply-To: <20181105194618.GA18731@jasmine.lan>
Hi
On 2018-11-05 20:46, Leo Famulari wrote:
> On Mon, Nov 05, 2018 at 07:13:22PM +0100, Björn Höfling wrote:
>> I would not consider this a bug: It clearly says that it is not a
>> proper URI. Also in the documentation all URLs/URIs are written in the
>> form of
>>
>> PROTOCOL://SERVER/PATH.
> I agree that it's not a bug, but perhaps it's more like a wishlist item.
>
> Ideally, users would not need to concern themselves with implementation
> details like protocol selection.
>
> Guix could offer a more unified or simpler interface for authorizing and
> selecting substitute servers, and it would handle server addresses,
> communication protocols, and key authorization. Currently it's very
> ad-hoc.
+1
It is error prone and hard to understand for newcomers what is going on
behind the scenes.
I wrote this report from the perspective of a newcomer - ideally they
should not receive any errors at all if you ask me.
Do you have any ideas how to implement anything better?
A newt-ncurses interface maybe?
--
Cheers
Swedebugia
next prev parent reply other threads:[~2018-11-05 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 23:41 bug#33261: [substitute-urls] Fails when given only "berlin.guixsd.org" swedebugia
2018-11-05 18:13 ` Björn Höfling
2018-11-05 19:46 ` Leo Famulari
2018-11-05 20:48 ` swedebugia [this message]
2018-11-05 21:01 ` Leo Famulari
2018-11-06 14:07 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62e5ca73-88e9-7e50-ea0c-f4a8f4c50dbf@riseup.net \
--to=swedebugia@riseup.net \
--cc=33261@debbugs.gnu.org \
--cc=bjoern.hoefling@bjoernhoefling.de \
--cc=leo@famulari.name \
/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.