X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=TFaebNiM70My//+t8Dhs7U1DPrw01b+qeC4ONTAcK0J
	Czn3MdPW24/KRb5bZAc0l19KNJeiN8xQJVoeUtQCXXi5mtz8WTDwor8OSOGGjkWZ
	gDcWKmdyy85j9W/sLvEGGEJL/jrkxTqaira0NEyTujJwhDzO7TZyWmu9IO3Py6rI
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=kQLDF+QgtHxrWd4hOITa/VfHNg0=; b=FoWcr7id9ES5+FqQj
	rZmtIwmeCFR6VofabA+wM45LYm8hdh1EZuNmC+rvN/dCG/VxM3+rMgAN8jGfDS29
	BifDL0fauGS7Wo8m28Ukn8NJXaSAuuoSRFZlJqQAAEZcHg+hzkQ0ztFxFdyEmCPa
	vyoxomNYeOc8baC1dRoqYuxv8k=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.1 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no version=3.3.2
X-HELO: out4-smtp.messagingengine.com
Message-ID: <52791688.20502@cwilson.fastmail.fm>
Date: Tue, 05 Nov 2013 11:02:16 -0500
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
Subject: Re: gcc-4.8.2-1: /bin/gcc fails
References: <52749A63 DOT 70803 AT acm DOT org> <20131102093635 DOT GB25012 AT calimero DOT vinschen DOT de> <5275D706 DOT 5030207 AT users DOT sourceforge DOT net> <20131104114204 DOT GB2731 AT calimero DOT vinschen DOT de> <5277B2F3 DOT 1060705 AT cwilson DOT fastmail DOT fm> <5278557C DOT 2090205 AT users DOT sourceforge DOT net> <20131105095221 DOT GA29697 AT calimero DOT vinschen DOT de>
In-Reply-To: <20131105095221.GA29697@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 11/5/2013 4:52 AM, Corinna Vinschen wrote:
> On Nov  4 20:18, Yaakov (Cygwin/X) wrote:
>> Under the circumstances, configuring inetutils with
>> --libexecdir=/usr/sbin makes the most sense.
>
> Full ACK.  Otherwise you'd have to provide some script which tweaks an
> existing /etc/inetd.conf to use the new paths.  Possible, but hardly
> worth the effort.

That's fine for me, but the other servers, maintained by others [1], 
which may or may not by started by inetd/xinetd would also need to 
configure as --libexecdir=/usr/sbin, or THEY would need to tweak 
configurations.

This seems...counter-intuitive. "cygwin follows the LSB and <the stuff> 
goes in /usr/libexec, except when it's too hard so there is the 
following list of exceptions...."  Is that the policy going forward?

I wasn't planning to auto-update config scripts. I was going to update 
the /etc/default/* scripts [2], and then WARN IN BIG LETTERS in the 
announcement that folks will need to manually merge the changes if 
they've modified their configuration files.  I know nobody will read it, 
but when the inevitable queries reach the mailing list I'll be able to 
point to the ANNOUNCE post.

[1] rsh-server, tftp-server, etc.

[2] this is WHY we have an /etc/default/ area after all -- to provide 
updates when configurations OUGHT to change, but without clobbering a 
user's customizations.  The downside, even on GNU/Linux, is that the 
user must manually merge.  Fedora provides tools to help do this, but it 
is still a manual process.

--
Chuck


--
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