From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: flex package POSIX violation
Date: Sun, 31 Dec 2017 22:34:00 -0000 [thread overview]
Message-ID: <5c53fe9c-fb4c-0013-e339-29a20da5ae0f@cygwin.com> (raw)
In-Reply-To: <3d6f4622-f4c2-b48c-7ba3-b353edd11bce@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 887 bytes --]
On 2017-12-31 15:44, Marco Atzeri wrote:
> On 31/12/2017 22:13, Steven Penny wrote:
>> The POSIX standard, at least since 1997 [1], requires the presence of
>> a "lex" utility.
>>
>> Most systems (including Cygwin) provide a Lex implementation via the
>> "flex"
>> package. However with other OS, a "lex -> flex" symlink is provided,
>> whereas the Cygwin package does not.
>
> Flex is NOT 100% Posix compliant.
> See Info on
> 20 Incompatibilities with Lex and Posix
> as upstream does not provide the link "lex -> flex"
> I am reluctant to do differently.
This is generally handled downstream, e.g.:
http://pkgs.fedoraproject.org/cgit/rpms/flex.git/tree/flex.spec#n90
https://packages.debian.org/sid/amd64/flex/filelist
https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-devel/flex/flex-2.6.4-r1.ebuild#n84
We should also do accordingly.
--
Yaakov
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2017-12-31 22:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 22:00 Steven Penny
2017-12-31 22:12 ` Marco Atzeri
2017-12-31 22:34 ` Yaakov Selkowitz [this message]
2017-12-31 23:43 ` Stephen John Smoogen
2018-01-05 14:37 ` Gerrit Haase
2018-01-06 0:17 ` Steven Penny
[not found] <CANnLRdjLkgpsw6ogipAVaAsjKm+fRruBFvizK-sgSNiXYWrijg@mail.gmail.com>
2018-01-01 0:26 ` Steven Penny
2018-01-01 0:55 ` Stephen John Smoogen
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=5c53fe9c-fb4c-0013-e339-29a20da5ae0f@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin@cygwin.com \
/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.
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).