From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Optional runtime dependencies in Guix
Date: Mon, 12 Jan 2015 19:47:30 +0100 [thread overview]
Message-ID: <20150112184614.GA4935@debian> (raw)
In-Reply-To: <87fvbgrmn9.fsf@gnu.org>
On Mon, Jan 12, 2015 at 05:26:02PM +0100, Ludovic Courtès wrote:
> To begin with, we could have a “weechat” package with a “reasonable”
> option set:
> (define weechat
> (make-weechat "weechat"))
>
> And possibly another variant with, say, all the options enabled:
> (define weechat-full
> (make-weechat "weechat-full" #:python? #t #:lua? #t))
So far, our policy has rather been to enable all possible inputs. I think
this should be the default with the name "weechat" unaltered. If need be,
one could add another package with fewer inputs under the name
"weechat-small" or similar.
What do others think? If there is consensus, we could formalise something
in the package naming section of the manual.
Apart from that, I do not see why having several scripting languages enabled
is a problem; in the end, it is quite likely that they are present anyway due
to one package or another (it is rather difficult to avoid perl and python
these days!). So my real preference would be to not have such "...-small"
packages except for outrageously big default packages (texlive comes to
mind here...).
> A long term possibility would be to officially support something like
> Gentoo’s “USE” flags. These would be declared as part of the package,
> and the build process would take them into account somehow:
To me, this sounds like overkill to solve a problem that I am not
convinced exists.
Andreas
next prev parent reply other threads:[~2015-01-12 18:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 3:43 Optional runtime dependencies in Guix Gammel Holte
2014-11-23 20:47 ` Ludovic Courtès
2015-01-11 15:38 ` Gammel Holte
2015-01-12 9:38 ` Ludovic Courtès
2015-01-12 11:23 ` Ricardo Wurmus
2015-01-12 16:03 ` Ludovic Courtès
2015-01-12 13:11 ` 宋文武
2015-01-12 16:26 ` Ludovic Courtès
2015-01-12 18:47 ` Andreas Enge [this message]
2015-01-12 19:18 ` Gammel Holte
2015-01-13 17:28 ` Ludovic Courtès
2015-01-13 17:24 ` 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=20150112184614.GA4935@debian \
--to=andreas@enge.fr \
--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.