unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: gobject-introspection typelibs and shared libraries
Date: Sat, 17 Jan 2015 13:02:44 +0100	[thread overview]
Message-ID: <20150117120244.GA8583@debian> (raw)
In-Reply-To: <CAKrPhPO0+rG7M5BiOoQWxsQTBr1xc00T24s+VSrLpDqDNy5bOg@mail.gmail.com>

On Sat, Jan 17, 2015 at 10:46:35AM +0100, Federico Beffa wrote:
> It would be the *GUIX project* the one who would benefit if decisions
> would be taken based on technical arguments and merits instead of
> feelings or the mood of the day.

Why do you suggest that my message was inspired by feelings or the mood
of the day? In fact, it was rather by the principles and design choices
we have made (without necessarily writing them down) in the past.
Especially with little available work power, I think it is important that we
do not make too many modifications to the upstream packages; there are
distributions out there with a tendency to become more or less upstream
themselves... On the long run, this would be a nightmare to maintain.

On Sat, Jan 17, 2015 at 11:47:20AM +0100, Ludovic Courtès wrote:
> John Darrington <john@darrington.wattle.id.au> skribis:
> > If we choose to do that, then for consistency we should also
> > do (setenv "LEX" "flex") and (setenv "YACC" "bison")  Possibly a few others too.
> Bah, this suggests that it’s a can of worms.

I think this makes exactly my technical point above...

Now we can and do make exceptions. About the particular issue, I do not
have very strong feelings. I fail to see why '(setenv "CC" "gcc")'
in cases where it is necessary poses major problems; but having a symlink
would also be okay. But if we go for the latter, I think you should bring
it up with the gcc project first.

Andreas

  parent reply	other threads:[~2015-01-17 12:02 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-17  9:46 gobject-introspection typelibs and shared libraries Federico Beffa
2015-01-17 10:15 ` 宋文武
2015-01-17 10:40 ` ‘gcc’ vs. ‘cc’ Ludovic Courtès
2015-01-17 10:44   ` John Darrington
2015-01-17 10:47     ` Ludovic Courtès
2015-01-17 12:02   ` Federico Beffa
2015-01-17 16:27     ` Ludovic Courtès
2015-01-17 12:02 ` Andreas Enge [this message]
2015-01-18  9:39   ` gobject-introspection typelibs and shared libraries Federico Beffa
2015-01-18 13:16     ` Andreas Enge
  -- strict thread matches above, loose matches on Subject: below --
2014-12-07 14:21 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
2015-01-15 21:42                                     ` Ludovic Courtès
2015-01-16 17:07                                       ` Federico Beffa
2015-01-16 20:47                                       ` 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=20150117120244.GA8583@debian \
    --to=andreas@enge.fr \
    --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).