From: kiasoc5 <kiasoc5@disroot.org>
To: guix-devel@gnu.org, zimon.toutoune@gmail.com,
h.goebel@crazy-compilers.com
Subject: Re: Guix-devel Digest, Vol 109, Issue 56
Date: Fri, 22 Jul 2022 17:12:09 +0000 [thread overview]
Message-ID: <20220722171209.312e2822@aria> (raw)
In-Reply-To: <mailman.5750.1658421830.1145.guix-devel@gnu.org>
Date: Thu, 21 Jul 2022 18:34:58 +0200
From: zimoun <zimon.toutoune@gmail.com>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>,
Guix-devel <guix-devel@gnu.org>
Subject: Re: native-inputs: Go for completeness or minimalism?
Message-ID: <86o7xi4e6l.fsf@gmail.com>
Content-Type: text/plain; charset=utf-8
Hi simon,
> On Wed, 20 Jul 2022 at 10:33, Hartmut Goebel
> <h.goebel@crazy-compilers.com> wrote:
>
> > Personally I tend to minimal.
>
> Me too. Being minimal is better on all aspects, IMHO.
>
> The only drawback is indeed “guix shell -D”. But, people developing
> can add the missing or extra packages. To me, Guix provides the
> minimal environment for building and running one package.
>
> Otherwise, we could imagine to create two packages.
>
> However, there is no consensus about this “minimalism”. For instance,
> some packages have multi-outputs which implies that “guix shell -D” is
> not minimal.
>
We could have packages recommend other packages to make this discovery
easier for users, like Arch's opt-depends.
> Cheers,
> simon
next parent reply other threads:[~2022-07-22 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5750.1658421830.1145.guix-devel@gnu.org>
2022-07-22 17:12 ` kiasoc5 [this message]
2022-07-22 17:16 ` Guix-devel Digest, Vol 109, Issue 56 Maxime Devos
2022-07-23 22:52 ` kiasoc5
2022-07-24 6:30 ` Liliana Marie Prikler
2022-09-03 10:58 ` zimoun
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=20220722171209.312e2822@aria \
--to=kiasoc5@disroot.org \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
--cc=zimon.toutoune@gmail.com \
/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).