From: John Darrington <john@darrington.wattle.id.au>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Symlinks to generic names
Date: Sun, 2 Feb 2014 08:46:58 +0100 [thread overview]
Message-ID: <20140202074657.GA3860@intra> (raw)
In-Reply-To: <87zjma3r40.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
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.
J'
--
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: 198 bytes --]
next prev parent reply other threads:[~2014-02-02 7:47 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 [this message]
2014-02-02 18:06 ` Ludovic Courtès
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
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=20140202074657.GA3860@intra \
--to=john@darrington.wattle.id.au \
--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 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).