all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "alírio eyng" <alirioeyng@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Proposal: Prefix language-name for language library packages
Date: Fri, 29 Apr 2016 19:36:32 -0400	[thread overview]
Message-ID: <20160429233632.GA13525@jasmine> (raw)
In-Reply-To: <CALkz57EYYR++04JVQAGRmNCkwW9WWT3=gTmo7aAx+snFZUu3=A@mail.gmail.com>

On Fri, Apr 29, 2016 at 06:31:24PM +0000, alírio eyng wrote:
> Ludovic Courtès:
> >what about multiple-language packages?  I’m thinking of
> >‘c+guile-guile’ and ‘c+siod+python-gimp’.
> the ideal categorization would be one output for each interface.
> so "guile" (scheme), "guile:c", "gimp" (gui), "gimp:c", "gimp:siod",
> "gimp:python", "emacs" (gui), "emacs:tui", "emacs:elisp" (to run
> "emacs -batch -eval").
> e.g. guile:c and emacs:tui are pretty useless for me, so i could not
> install them.
> it's worth to focus on packages already split: "emacs" (gui+tui+elisp)
> and "emacs:no-gui" (tui+elisp), linux-libre, ...

I don't think we should split packages up unless there is a pressing
reason to do it. For example, some our packages have a rarely-used
component that uses a lot of disk space or has a very large dependency.
It makes sense to put those in different outputs.

But if we go too far, nobody will be able to tell which package to
install to accomplish their task.

> c nomenclature:
> packages with c interface currently have nothing, "lib" (prefix or
> postfix), "c-", "-c", "4c" or "-headers".
> e.g. "readline" "libunistring" "htslib" "c-ares" "json-c" "icu4c"
> "mesa-headers" "linux-libre-headers".
> and lots of synopses with nothing, "C library for", "C library
> providing", "C library to", "implementation in C" or "written in C".

Again, unless some package's headers take up a large amount of disk
space, or have some other onerous cost, I don't see a reason to put them
in a separate output.

  reply	other threads:[~2016-04-29 23:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28  8:45 Proposal: Prefix language-name for language library packages alírio eyng
2016-04-29 18:31 ` alírio eyng
2016-04-29 23:36   ` Leo Famulari [this message]
2016-04-30  6:38     ` Ricardo Wurmus
2016-05-02  7:50       ` Ludovic Courtès
2016-05-02  9:33         ` ng0
2016-05-02 18:33         ` Leo Famulari
2016-05-06  2:45           ` alírio eyng
2016-05-06  6:49             ` Ricardo Wurmus
2016-05-06 10:20               ` Ludovic Courtès
2016-05-06 20:12             ` Andreas Enge
2016-05-07  0:32               ` John Darrington
2016-05-01  3:00     ` alírio eyng
  -- strict thread matches above, loose matches on Subject: below --
2016-04-24 13:22 Hartmut Goebel
2016-04-24 16:00 ` Danny Milosavljevic
2016-04-24 18:57 ` Leo Famulari
2016-04-24 22:13   ` Hartmut Goebel
2016-04-28 11:48   ` Ludovic Courtès
2016-04-28 11:56 ` Ludovic Courtès
2016-04-28 16:04   ` Leo Famulari

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=20160429233632.GA13525@jasmine \
    --to=leo@famulari.name \
    --cc=alirioeyng@gmail.com \
    --cc=guix-devel@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.