From: Federico Beffa <beffa@ieee.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: gobject-introspection typelibs and shared libraries
Date: Thu, 15 Jan 2015 09:27:17 +0100 [thread overview]
Message-ID: <CAKrPhPNgJw7YNdhL4+AOZm1cS0d+A5yioYr-U65JpH=e0KQQiA@mail.gmail.com> (raw)
In-Reply-To: <87wq4p3xfe.fsf@gnu.org>
On Wed, Jan 14, 2015 at 9:43 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>>> So far we’ve resisted the temptation, and it’s rarely been an issue.
>>> :-)
>>
>> Could you elaborate on the down sides? (I'm not trying to insist, but to learn.)
>
> Basically it’s good to stick to what GCC does, and GCC does not install
> ‘cc’. There’s a subjective aesthetic downside: it’s good to spread the
> ‘g’. And also, it turns out to work for 99% of the packages.
OK, I thought you were referring to technical reasons...
A different look at aesthetics: Back in the mid '90, when Linux was
still an underground curiosity, many UNIX admins were starting to
install GNU user-land applications. To avoid name clashes with the
vendor versions of programs they were prefixing all GNU applications
with a 'g'. So, the GNU version of 'ls' was named 'gls', 'awk' ->
'gawk', ... Now on GNU/Linux systems there's no need for such
prefixing and, for consistency and to send a message, you may just
name the C compiler with the traditional name 'cc' which means: Hey,
this is the official system C compiler and of course, it's the GNU
one.
Regards,
Fede
next prev parent reply other threads:[~2015-01-15 8:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 14:21 gobject-introspection typelibs and shared libraries Federico Beffa
2014-12-07 20:48 ` Ludovic Courtès
2014-12-07 22:11 ` Federico Beffa
2014-12-08 9:22 ` Ludovic Courtès
2014-12-08 12:21 ` Federico Beffa
2014-12-08 14:51 ` Federico Beffa
2014-12-08 20:37 ` Ludovic Courtès
2014-12-09 19:30 ` Federico Beffa
2014-12-09 20:27 ` Federico Beffa
2014-12-10 4:15 ` Mark H Weaver
2014-12-09 20:58 ` Ludovic Courtès
2014-12-10 4:39 ` Mark H Weaver
2014-12-10 4:54 ` Mark H Weaver
2014-12-10 8:48 ` Ludovic Courtès
2014-12-10 8:57 ` Federico Beffa
2014-12-10 12:56 ` Ludovic Courtès
2014-12-16 19:45 ` Federico Beffa
2014-12-17 7:20 ` Mark H Weaver
2014-12-17 8:57 ` Ludovic Courtès
2015-01-13 17:10 ` Federico Beffa
2015-01-13 20:22 ` Ludovic Courtès
2015-01-13 21:40 ` Federico Beffa
2015-01-14 20:43 ` Ludovic Courtès
2015-01-15 8:27 ` Federico Beffa [this message]
2015-01-15 21:42 ` Ludovic Courtès
2015-01-16 17:07 ` Federico Beffa
2015-01-16 20:47 ` Andreas Enge
-- strict thread matches above, loose matches on Subject: below --
2015-01-17 9:46 Federico Beffa
2015-01-17 10:15 ` 宋文武
2015-01-17 12:02 ` Andreas Enge
2015-01-18 9:39 ` Federico Beffa
2015-01-18 13:16 ` Andreas Enge
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='CAKrPhPNgJw7YNdhL4+AOZm1cS0d+A5yioYr-U65JpH=e0KQQiA@mail.gmail.com' \
--to=beffa@ieee.org \
--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.