This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: MSYS mode (continue)
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-developers at cygwin dot com
- Date: Fri, 26 Jul 2013 18:16:49 +0200
- Subject: Re: MSYS mode (continue)
- References: <20130705090704 dot GB4009 at calimero dot vinschen dot de> <20130705164230 dot GA7282 at ednor dot casa dot cgf dot cx> <20130711111744 dot GG15346 at calimero dot vinschen dot de> <51F123EB dot 9000900 at cwilson dot fastmail dot fm> <20130725150209 dot GA15619 at calimero dot vinschen dot de> <51F16C82 dot 7030509 at cwilson dot fastmail dot fm> <20130725205320 dot GA2725 at ednor dot casa dot cgf dot cx> <20130726081510 dot GN5086 at calimero dot vinschen dot de> <20130726151432 dot GA4495 at ednor dot casa dot cgf dot cx> <51F29A3D dot 2060207 at gmail dot com>
- Reply-to: cygwin-developers at cygwin dot com
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