From: Leo Famulari <leo@famulari.name>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel@gnu.org
Subject: Re: Proposal: Prefix language-name for language library packages
Date: Sun, 24 Apr 2016 14:57:15 -0400 [thread overview]
Message-ID: <20160424185715.GC7737@jasmine> (raw)
In-Reply-To: <571CC87B.8010603@crazy-compilers.com>
On Sun, Apr 24, 2016 at 03:22:03PM +0200, Hartmut Goebel wrote:
> Hi,
>
> I propose to generalizing the specification [1,2] as we already have for
> Perl, Python and Java for most programming languages. In short:
>
> Package names should be prefixed with the name of the language and if
> the package name already contains the name of the language, it gets
> removed there.
>
> I quickly scanned the current package definitions and found:
>
> guile: 2 package to change
> haskell: ca. 2 package to be changed
> julia: 0
> d (lcd.xscm): 0
> nqc (lego.scm): 0 --> prefix "lego-"? OTOH this is a commercial brand
> lua: 0
> m4: 0
> ocaml: 1
> ruby: 0
> r (statistics.scm): 0
> scheme: 1 or 2
> smalltalk: 0
> tcl: 0
What about C? Do we need c-linux-libre? ;)
next prev parent reply other threads:[~2016-04-24 18:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 13:22 Proposal: Prefix language-name for language library packages Hartmut Goebel
2016-04-24 16:00 ` Danny Milosavljevic
2016-04-24 18:57 ` Leo Famulari [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2016-04-28 8:45 alírio eyng
2016-04-29 18:31 ` alírio eyng
2016-04-29 23:36 ` Leo Famulari
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
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=20160424185715.GC7737@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.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).