From: myglc2 <myglc2@gmail.com>
To: 22600@debbugs.gnu.org
Subject: bug#22600: 'Globally-Visible Packages' not shown by 'M-x guix-installed-packages'
Date: Tue, 09 Feb 2016 21:30:28 -0500 [thread overview]
Message-ID: <87bn7p5mbf.fsf@gmail.com> (raw)
In-Reply-To: <87zivb6xyy.fsf@gmail.com>
Alex Kost <alezost@gmail.com> writes:
> myglc2 (2016-02-09 05:29 +0300) wrote:
> [...]
>> My concern is that this experience might leave a new user thinking,
>> "Geez, I know back in the fog of the USB install I added packages. What
>> kind of package manager is this? It doesn't show me the packages that I
>> painfully typed in using zile at the console". IMO this is the kind of
>> doubt that can undermine confidence during the critical first few hours
>> of software test driving and lead a user to abandon the experment.
>
> I would say that a user should get acquainted with the basic concepts of
> Guix before using it. I think per-user package management is one of such
> concepts, and it is described in the beginning of (info "(guix) Features")
> section of the manual.
>
Per-user features are very important for guix adopters. But as
described in my other post, global (aka system) features are equally
important for guixSD adopters. It is fantastic that guix + guixSD
support both use cases.
OTOH, these use cases appear to be fighting against each other. This
makes the documentation hard to write and understand. It makes the
user interface hard to do. If we let the conflict get out of control
it will confuse the marketplace and undermine guix/SD.
So we need to embrace and understand this natural yin and yang in a
great solution that spans user, package, distribution, and system
managment. If we can do that I think guix/SD will be very successful.
>> But, wouldn't it be better to combine these functions so even a duummy
>> will see all the packages?
>
> As I suggested in the previous mail, we can add "M-x guix-system-packages".
> Maybe it would be good to add "M-x guix-user-packages", or maybe name them:
>
> - guix-installed-system-packages (for /run/current-system/profile)
> - guix-installed-user-packages (for ~/.guix-profile)
>
> And to leave "M-x guix-installed-packages" for an arbitrary profile
> specified by a user. WDYT?
I like it. I tried to summarize what I think I understand in the table
below. Could you take a look and fix it up?
| Recipe Source | install | Profile | UI access | Scope | Generations |
|-------------------------+----------------------------------------------------------------------------+-----------------------------+--------------------------------------+--------+-----------------------------|
| guix pull | sudo guix system reconfigure <config> | /run/current-system/profile | * M-x guix-installed-system-packages | global | M-x guix-system-generations |
| guix pull | guix -i <package> | ~/.guix-profile | * M-x guix-installed-user-packages | global | M-x guix-generations |
| | | | | | |
| git pull w/wo user mods | [env]$ sudo ./pre-inst-env guix system reconfigure ../configs/config.k.scm | /run/current-system/profile | * M-x guix-installed-system-packages | user | M-x guix-system-generations |
| git pull w/wo user mods | ??? | ~/.guix-profile | * M-x guix-installed-user-packages | user | M-x guix-generations |
| | | | | | |
| <user custom> | ??? | <user specfied> | M-x guix-installed-packages | ouser | ??? |
| | | | | | |
Notes:
* - proposed
??? - don't know
next prev parent reply other threads:[~2016-02-10 2:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 15:08 bug#22600: 'Globally-Visible Packages' not shown by 'M-x guix-installed-packages' myglc2
2016-02-08 21:58 ` Alex Kost
2016-02-08 22:51 ` Ludovic Courtès
2016-02-09 2:29 ` myglc2
2016-02-09 19:21 ` Alex Kost
2016-02-10 2:30 ` myglc2 [this message]
2016-02-10 9:04 ` Alex Kost
2016-02-10 20:25 ` myglc2
2016-02-13 20:37 ` Alex Kost
2016-02-22 19:55 ` Alex Kost
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=87bn7p5mbf.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=22600@debbugs.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.