unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Guix System video review on YouTube
Date: Mon, 27 Apr 2020 11:08:47 +0200	[thread overview]
Message-ID: <CAJ3okZ2=ASF4iWi=2E8UAwve=2=C1KyMk8kntUNb-4wW2tLghw@mail.gmail.com> (raw)
In-Reply-To: <855dde2f-a7c7-d6e4-b649-a3bae60f99cb@web.de>

Hi Jonathan,

Thank you for translating the feedback.
Because watching without understand German feels like "Guix is so cool!" ;-)


On Mon, 27 Apr 2020 at 00:34, Jonathan Brielmaier
<jonathan.brielmaier@web.de> wrote:

> * There is no /etc/os-release file. I think it was proposed a while ago,
> but the patch was rejected.

Naive question: what is useful for?
And what does it mean on rolling-release distro?


> * While installing packages via `guix install` you can't scroll in the
> terminal, you always get reset to the bottom.

I missed what it mean. Could you quickly extend a bit?


> * guix show/search does not show if a package is installed.

Installed where? In which profile?
I am not sure that "installed" make sense at the level of "guix show/search".

From my point of view, it could be interesting to know if the package
is already available in the store. Basically, if "guix build
--dry-run" completes all the recursive phases without download or
build. For a couple of packages (guix show), it is doable but it is
too much expensive for "guix search".

WDYT?


> * `guix search ... | less can be confusing at the beginning.

There is room of improvements for "guix search". ;-)

There is 3 behaviours
 1. return the N packages fitting the screen size (current: default)
 2. display all the list in PAGER (current: |less)
 3. display all the list in stdout (current: |cat)

The feature request is: be able to configure which behaviour by
default for "guix search". Maybe via an environment variable.
(as discussed elsewhere by Ricardo and Tobias, if I understand correctly)


WDYT?


What user expect by default is complicated and depends on the users
themself. :-)
For example, I always pipe with 'recsel' because coming from Debian
and used to 'aptitude', I only want the name of the package and then
show more if I need; i.e.,

   guix search crypto library | recel -C -P name
   # optional: time to time I pipe the result with 'grep'
   guix show libb2

Well, I find more confusing that "guix search" displays
name,synopsis,description,etc. than to pipe. So, taste and colour...
;-)


> * Multi user package concept not clear (root as different packages then
> normal user).

This is related to expectation about "installed", IMHO.


Thank you for the feedback. Really interesting!

Cheers,
simon

  parent reply	other threads:[~2020-04-27  9:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26 22:32 Guix System video review on YouTube Jonathan Brielmaier
2020-04-27  6:16 ` Jan Nieuwenhuizen
2020-04-27  9:08 ` zimoun [this message]
2020-04-27 10:11   ` Jonathan Brielmaier
2020-04-27 12:44     ` zimoun
2020-04-27 17:37       ` Bengt Richter
2020-04-28  0:32     ` raingloom
2020-04-28 11:04       ` Bengt Richter
2020-04-28 11:11         ` Jonathan Brielmaier
2020-04-27 10:20   ` Efraim Flashner
2020-04-27 10:20 ` Danny Milosavljevic

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to='CAJ3okZ2=ASF4iWi=2E8UAwve=2=C1KyMk8kntUNb-4wW2tLghw@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=jonathan.brielmaier@web.de \
    /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 public inbox

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

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).