DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=EMPmC+SmuE2KOK9M
	/7vo26n1zeytPtCJnVHhG1WEt/nYytV42cMEaAav1ShzG+SHzkMcMwY7HoWP48oO
	t0G1XBOeqH48tYuZw1w0lNKWg2ahjZjs/14T/gPOKhuXcdeIYpa1OZ4e2bp0Rx0i
	VR7ROxA8ezPiWtbvExPj4wH51rE=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: Standard LEX variable doesn't work in Make.
To: cygwin@cygwin.com
References: <d06883e8208624afb5d094ebd3e78375@mail.kylheku.com> <11448207-52c8-6745-999f-48a4534bbc41@t-online.de> <eee3ac0a-6715-1517-9045-2e2ac8544c66@SystematicSw.ab.ca> <4805811d-559f-a49d-9b2f-5041a0b94b08@t-online.de> <8af64289-18cd-d14a-0fea-10e80d2752f8@SystematicSw.ab.ca>
From: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= <HBBroeker@t-online.de>
Message-ID: <357b8785-5a7f-7d64-180c-9ee410fe8d86@t-online.de>
Date: Sat, 26 Nov 2016 22:42:45 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0
MIME-Version: 1.0
In-Reply-To: <8af64289-18cd-d14a-0fea-10e80d2752f8@SystematicSw.ab.ca>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Am 26.11.2016 um 04:42 schrieb Brian Inglis:

> On Debian both yacc and bison.yacc are alternatives;

Not exactly.  bison.yacc is a script; the same one that Cygwin's bison 
package installed as /usr/bin/yacc.  Debian obviously renamed it.  They 
have to do that because their yacc is an alternative.  And that's 
because there are at least 4 programs available in the package 
repository that can fulfill that role: bison, bison++, byacc and btyacc.

Nor do they use alternatives to build their symlink lex -> flex.

>> I don't think 'alternatives' is applicable here. We're not looking at
>> several packages providing the same file --- we're looking at
>>
>> * single packages offering the same executable under more than one
>> name, causing it to express different personalities, like ex ->
>> vi.exe, view -> vi.exe, latex --> pdftex.exe,
>
> and all vi, vim, nvi, elvis etc. links are handled via alternatives:
> it's used as the canonical example in

... the canonical example for multiple packages supplying the same 
program, 'vi'.  Cygwin has only 'vim', not nvi or elvis, so there's no 
need for the alternatives mechanism.

Just because alternative manages symlinks in /usr/bin, that doesn't mean 
every symlink in /usr/bin has to, or even should, be managed by it.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple