From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: gcc-4.8.2-1: /bin/gcc fails
Date: Tue, 05 Nov 2013 16:18:00 -0000 [thread overview]
Message-ID: <20131105161842.GB2499@calimero.vinschen.de> (raw)
In-Reply-To: <52791688.20502@cwilson.fastmail.fm>
[-- Attachment #1: Type: text/plain, Size: 1907 bytes --]
On Nov 5 11:02, Charles Wilson wrote:
> 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 can't exactly read Yaakov's brain, but to me the idea here is to
keep the changes for the *user* small and working even after an
update, rather than following the guidelines slavishly.
> 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.
rsh-server is your package.
tftp-server *explicitely* installes into /usr/sbin aka --sbindir.
sshd is installed into sbindir as well, btw., and not only on Cygwin,
but upstream.
Looks like there should nothing change, in fact.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-11-05 16:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 6:23 David Rothenberger
2013-11-02 9:36 ` Corinna Vinschen
2013-11-03 4:54 ` Yaakov (Cygwin/X)
2013-11-03 19:22 ` David Rothenberger
2013-11-04 11:42 ` Corinna Vinschen
2013-11-04 14:45 ` Charles Wilson
2013-11-04 17:35 ` Andrey Repin
2013-11-05 2:18 ` Yaakov (Cygwin/X)
2013-11-05 9:52 ` Corinna Vinschen
2013-11-05 16:03 ` Charles Wilson
2013-11-05 16:18 ` Corinna Vinschen [this message]
2013-11-05 3:05 ` Andrey Repin
2013-11-05 3:39 ` Robert Pendell
2013-11-05 4:20 ` Robert Pendell
2013-11-05 6:35 ` Andrey Repin
2013-11-10 18:08 ` Bengt Larsson
2013-11-22 19:02 ` jojelino
2013-11-22 19:36 ` jojelino
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=20131105161842.GB2499@calimero.vinschen.de \
--to=corinna-cygwin@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).