From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Emacs interface for Guix
Date: Mon, 21 Jul 2014 22:46:13 +0400 [thread overview]
Message-ID: <8761iqr1my.fsf@gmail.com> (raw)
In-Reply-To: <87k3764s1c.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 21 Jul 2014 18:04:31 +0200")
Ludovic Courtès (2014-07-21 20:04 +0400) wrote:
> Alex Kost <alezost@gmail.com> skribis:
>
>> I think current situation is very confusing to users. A user can't even
>> install any package. What if he wants to install “guile” from
>> “base.scm”?
>
> It’s possible, using ‘guix package -e’ (info "(guix) Invoking guix
> package").
>
> I think guix.el should be able to distinguish packages internally, so
> that when I choose, say, a specific “guile-2.0.11”, that’s really the
> one that gets installed (maybe it already does, I haven’t checked.)
No it doesn't and I don't see how it can be done. If it were Guile
Emacs, it would be possible to distinguish packages internally, but all
I have now is name+version which is not unique. Or maybe...
>> I strongly believe this is a problem. You can see the packages that you
>> can't install or even worse “guix package --list-installed” may tell you
>> that you have several “foo-1.0:out” installed. Actually when I saw the
>> packages with the same name/version the first time, I thought it's a
>> bug.
>
> I would say it’s a problem of the distro–i.e., the (gnu packages ...)
> modules–if several same-named packages are exposed to the user. We’ve
> discussed several times the problem of having duplicates between
> base.scm and other modules, but I haven’t come to a satisfying solution.
>
> So I agree, these specific cases must be addressed somehow.
>
> However, it’s a fundamental feature of the package manager that packages
> (really: package records) can be freely created, and that the ‘name’
> field is just a hint. Duplicates should remain rare in practice, but
> the UI must be prepared to deal with them IMO.
>
> WDYT?
... or maybe this: to fill some hash table or vhash or whatever with all
available packages after a repl is started, and use this storage with
unique keys to search/get packages instead of the ‘fold-packages’. This
will allow to get and thus to install a particular package by its key.
I didn't think much about it, but right now this is the only workaround
I can imagine. What do you think?
next prev parent reply other threads:[~2014-07-21 18:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 5:59 Emacs interface for Guix Alex Kost
2014-07-16 14:18 ` Ludovic Courtès
2014-07-16 19:05 ` Alex Kost
2014-07-18 9:16 ` Ludovic Courtès
2014-07-19 7:51 ` Alex Kost
2014-07-19 16:28 ` Ludovic Courtès
2014-07-20 7:10 ` Alex Kost
2014-07-20 14:08 ` Ludovic Courtès
2014-07-20 16:52 ` Alex Kost
2014-07-20 19:42 ` Alex Kost
2014-07-20 19:47 ` Ludovic Courtès
2014-07-21 6:46 ` Alex Kost
2014-07-21 16:04 ` Ludovic Courtès
2014-07-21 18:46 ` Alex Kost [this message]
2014-07-21 21:26 ` Ludovic Courtès
2014-07-22 6:20 ` Alex Kost
2014-07-22 6:53 ` Taylan Ulrich Bayirli/Kammer
2014-07-22 8:41 ` Ludovic Courtès
2014-07-22 9:34 ` Alex Kost
-- strict thread matches above, loose matches on Subject: below --
2014-07-25 17:58 Alex Kost
2014-07-25 20:36 ` Ludovic Courtès
2014-07-26 17:44 ` Alex Kost
2014-07-28 10:15 ` Alex Kost
2014-08-11 20:54 ` Ludovic Courtès
2014-08-12 10:19 ` [PATCH] " Alex Kost
2014-08-12 14:19 ` Ludovic Courtès
2014-08-12 16:20 ` Alex Kost
2014-08-12 19:50 ` Ludovic Courtès
2014-08-13 6:57 ` Alex Kost
2014-08-13 16:03 ` Ludovic Courtès
2014-08-13 20:58 ` Alex Kost
2014-08-16 12:24 ` Ludovic Courtès
2014-08-16 13:07 ` Alex Kost
2014-08-19 21:00 ` Ludovic Courtès
2014-08-20 10:54 ` Alex Kost
2014-08-22 8:56 ` Ludovic Courtès
2014-08-22 12:44 ` Alex Kost
2014-08-27 8:34 ` Ludovic Courtès
2014-07-26 20:58 ` 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=8761iqr1my.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.