unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: gobject-introspection typelibs and shared libraries
Date: Wed, 14 Jan 2015 21:43:49 +0100	[thread overview]
Message-ID: <87wq4p3xfe.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPMgGiHiRSOH-+f+Hns-GzRDLzk=zcRH2+7fQyY1i_3J1Q@mail.gmail.com> (Federico Beffa's message of "Tue, 13 Jan 2015 22:40:20 +0100")

Federico Beffa <beffa@ieee.org> skribis:

> On Tue, Jan 13, 2015 at 9:22 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>> Federico Beffa <beffa@ieee.org> skribis:
>>
>>> The question is: do we want to make a 'cc' symlink to 'gcc' in the
>>> 'gcc' package?
>>
>> 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.

(I’m afraid this answer may disappoint you.  ;-))

Ludo’.

  reply	other threads:[~2015-01-14 20:44 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 [this message]
2015-01-15  8:27                                   ` Federico Beffa
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

  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=87wq4p3xfe.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=beffa@ieee.org \
    --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).