From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30162 invoked by alias); 26 Jul 2013 16:16:59 -0000 Mailing-List: contact cygwin-developers-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner@cygwin.com Mail-Followup-To: cygwin-developers@cygwin.com Received: (qmail 30134 invoked by uid 89); 26 Jul 2013 16:16:58 -0000 X-Spam-SWARE-Status: No, score=0.2 required=5.0 tests=AWL,BAYES_50,RDNS_NONE autolearn=no version=3.3.1 Received: from Unknown (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Fri, 26 Jul 2013 16:16:57 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 7AE505200F5; Fri, 26 Jul 2013 18:16:49 +0200 (CEST) Date: Fri, 26 Jul 2013 16:16:00 -0000 From: Corinna Vinschen To: cygwin-developers@cygwin.com Subject: Re: MSYS mode (continue) Message-ID: <20130726161649.GS5086@calimero.vinschen.de> Reply-To: cygwin-developers@cygwin.com Mail-Followup-To: cygwin-developers@cygwin.com References: <20130705090704.GB4009@calimero.vinschen.de> <20130705164230.GA7282@ednor.casa.cgf.cx> <20130711111744.GG15346@calimero.vinschen.de> <51F123EB.9000900@cwilson.fastmail.fm> <20130725150209.GA15619@calimero.vinschen.de> <51F16C82.7030509@cwilson.fastmail.fm> <20130725205320.GA2725@ednor.casa.cgf.cx> <20130726081510.GN5086@calimero.vinschen.de> <20130726151432.GA4495@ednor.casa.cgf.cx> <51F29A3D.2060207@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <51F29A3D.2060207@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2013-07/txt/msg00042.txt.bz2 On Jul 26 19:48, LRN wrote: > On 26.07.2013 19:14, Christopher Faylor wrote: > > On Fri, Jul 26, 2013 at 10:15:10AM +0200, Corinna Vinschen wrote: > > I don't think that we should be seeing the word "msys" throughout the > > DLL source code. The hooks could all be just named "cygwin_hook" > > generic and, maybe we should recognize something like a > > "CYGWIN=PRELOAD=MSYS.dll". I don't know how the MSYS folks would > > feel about that however. Having to tell their users that they need > > to set an environment variable before they do anything seems like it > > would be a maintenance headache. > MSYS actually does require an environment variable to be set. > MSYSTEM=MINGW32 or MSYSTEM=MSYS (at least MSYS1 did, if you wanted to > use it with MinGW, and MSYS2 does, in its current form). Most users must > have MSYSTEM=MINGW32, otherwise their build system type will be > misdetected (as MSYSTEM affects the name returned by uname() syscall). > > In MSYS1 this was done by the msys.bat batch file that was used to > launch the shell. So that shouldn't be much of a problem. > > As far as /etc/fstab is concerned, since they were the first to > > implement the notion, I would assume that they don't want to have to > > tell their userbase to change any more than we would want to have to > > tell every Cygwin user that they have to edit a file to make the > > next version of Cygwin work correctly. > > I wouldn't worry about this too much. MSYS2, being nearly pure Cygwin, > may require more elaborate installation procedures than MSYS1 did. These > procedures could include an /etc/fstab conversion script, if users > upgrade from MSYS1. > > MSYS1 compatibility might be interesting for some people (for mingw.org > - - definitely), but not for everyone. Wouldn't a generic conversion script be in order then, which also enforces the noacl setting if desired? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat