all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: Symlinks to generic names
Date: Sun, 02 Feb 2014 19:06:20 +0100	[thread overview]
Message-ID: <87bnyp4cf7.fsf@gnu.org> (raw)
In-Reply-To: <20140202074657.GA3860@intra> (John Darrington's message of "Sun, 2 Feb 2014 08:46:58 +0100")

John Darrington <john@darrington.wattle.id.au> skribis:

> On Sun, Feb 02, 2014 at 08:34:23AM +0100, Ludovic Courtès wrote:
>      John Darrington <john@darrington.wattle.id.au> skribis:
>      
>      > Some software (rightly or wrongly) tries to build with "lex" and "yacc" .  Guix does not provide these.
>      > Instead we have "flex" and "bison".  Most operating systems have symbolic links lex -> flex and yacc -> bison.
>      > Shouldn't we provide these too?
>      
>      We had a similar discussion for ‘cc’ vs. ‘gcc’, but in practice ‘cc’ has
>      been rare enough that it’s not worth bothering.
>
>      I believe Autoconf-based packages do not have any problems with ‘flex’
>      and ‘bison’.  What package was it?  How hard is it to work around?
>      
> It's probably not too hard.  It just seems to me, that it makes more sense to do the 
> workaround in 1 package, than in N.

I understand the point, but that does not answer my question.  :-)

I mean, I don’t think it’s worth discussing it until we have at least
two or more occurrences of the problem.

Ludo’.

  reply	other threads:[~2014-02-02 18:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-01  8:21 Symlinks to generic names John Darrington
2014-02-01 18:28 ` Nikita Karetnikov
2014-02-02  0:32   ` Mark H Weaver
2014-02-02  7:34 ` Ludovic Courtès
2014-02-02  7:46   ` John Darrington
2014-02-02 18:06     ` Ludovic Courtès [this message]
2014-02-02 13:40   ` John Darrington
2014-02-02 16:42     ` Andreas Enge
2014-02-02 17:47       ` John Darrington
2014-02-03 13:46         ` Ludovic Courtès

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=87bnyp4cf7.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=john@darrington.wattle.id.au \
    /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.