From: John Darrington <john@darrington.wattle.id.au>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org, al?rio eyng <alirioeyng@gmail.com>
Subject: Re: Proposal: Prefix language-name for language library packages
Date: Sat, 7 May 2016 02:32:32 +0200 [thread overview]
Message-ID: <20160507003232.GA18243@jocasta.intra> (raw)
In-Reply-To: <20160506201214.GA2432@solar>
[-- Attachment #1: Type: text/plain, Size: 1928 bytes --]
On Fri, May 06, 2016 at 10:12:14PM +0200, Andreas Enge wrote:
On Fri, May 06, 2016 at 02:45:48AM +0000, al?rio eyng wrote:
> i suggested renaming:
> readline, libunistring, htslib, c-ares, json-c, icu4c, ...
> to:
> c-readline, c-unistring, c-hts, c-ares, c-json, c-icu, ...
> no replies, is that implicit agreement?
I did not follow the discussion in all its details, but thought this part
was an obvious joke to illustrate the limits of the suggestion...
C being the natural GNU language and C++ its extension, I see no reason
to emphasise that a package is written in C.
Part of why we added a language prefix (for perl, I think, or maybe python
came first?) was also that the libraries had rather generic names. There
is perl-error, perl-html-form, perl-json and so on (not to speak of
perl-xyz containing bindings to some C library called xyz); we feared there
would be many collisions with existing C libraries and tools or further
interpreted languages.
Some packages already have rediculously long names. I don't see a need to make them
longer. In fact, I would like to make some of them shorter. For example:
perl-moosex-emulate-class-accessor-fast
perl-catalyst-plugin-authorization-roles
perl-catalyst-traitfor-request-proxybase
perl-moosex-types-datetime-morecoercions
perl-catalyst-plugin-session-state-cookie
perl-plack-middleware-removeredundantbody
perl-catalyst-component-instancepercontext
perl-catalyst-plugin-session-store-fastmmap
perl-catalyst-authentication-store-dbix-class
perl-plack-middleware-fixmissingbodyinredirect
J'
--
Avoid eavesdropping. Send strong encryted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-05-07 0:33 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
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 [this message]
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
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=20160507003232.GA18243@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=alirioeyng@gmail.com \
--cc=andreas@enge.fr \
--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 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).