unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Vollmert <rob@vllmrt.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: distinguishing between applications and libraries
Date: Tue, 2 Jul 2019 15:35:18 +0200	[thread overview]
Message-ID: <626A5DF1-310E-4FEC-8A8D-CE8A78BCA066@vllmrt.net> (raw)
In-Reply-To: <87lfxhv322.fsf@elephly.net>



> On 1. Jul 2019, at 23:48, Ricardo Wurmus <rekado@elephly.net> wrote:
>> - `guix search` would ignore library packages by default
> 
> I think it’s valid for users to want to install libraries.  For Python,
> for example, installing modules that don’t provide any executables
> appears to be the norm.

The idea would be that

`guix search <topic>`

would find applications related to topic, while e.g.

`guix search [-l|--include-libraries] <topic>`

would include library packages. So installing libraries would still
be possible.

(It needn’t be a “application vs library” distinction either, it could
be “graphical vs command line” or “user vs development” or whatever.)

Robert

  reply	other threads:[~2019-07-02 13:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-30 17:33 distinguishing between applications and libraries Robert Vollmert
2019-06-30 18:01 ` Pierre Neidhardt
2019-06-30 20:05   ` Robert Vollmert
2019-06-30 21:20     ` Pierre Neidhardt
2019-07-01 21:46       ` Ricardo Wurmus
2019-07-01 22:02         ` Pierre Neidhardt
2019-07-02  6:51           ` Ricardo Wurmus
2019-07-02  0:24     ` Jakob L. Kreuze
2019-07-02  6:55       ` Ricardo Wurmus
2019-07-02 15:24         ` Jakob L. Kreuze
2019-07-01  8:30 ` Danny Milosavljevic
2019-07-01 11:29   ` Pierre Neidhardt
2019-07-01 21:48 ` Ricardo Wurmus
2019-07-02 13:35   ` Robert Vollmert [this message]
2019-07-02 14:33     ` zimoun
2019-07-05 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

  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=626A5DF1-310E-4FEC-8A8D-CE8A78BCA066@vllmrt.net \
    --to=rob@vllmrt.net \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).