DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:date:message-id:subject:from:to
	:content-type; q=dns; s=default; b=rO90L34D3B+xOxlPubf8YfS/IJe8B
	j6g/crG+cyA4E+fLzv2eyGaYHEUIoQtQ6Cdg9/pEhPoHXlgq8xhnhh1SZ8Zd/Vqa
	ShcyU6DQ7h6CWPpa4AIS1u8C2AMqX0c+xvX6wXOHIa5j8yzdoBj62/0FQ8J4AMs5
	cMmsqxHoGWs0Jg=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Date: Tue, 18 Jun 2013 22:40:36 +0400
Message-ID: <CABEPuQJDLjtbcLig1isTUJgb6RBCD8LNShbm9mTPcb9WM5S5fw@mail.gmail.com>
Subject: Adding MSYS functionality to Cygwin
From: =?KOI8-R?B?4czFy9PFyiDwwdfMz9c=?= <alexpux AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1

Hi everybody!

I want to add MSYS functionality to Cygwin.
More than 10 years ago Cygwin 1.3 had forked to MSYS. But now this
MSYS is very old and don't has any support for it.
Primary goal of MSYS is to provide environment with GNU utilities for
building application using native Mingw compilers. The main
differences from original Cygwin is working with native Win32
applications.
So I create new MSYS based on last Cygwin and it works good I think.
But I think that the right way is to implement MSYS functionality in
Cygwin sources directly because in this case we don't need to do many
copies of different Cygwin dll with other names. And we always has
latest work from Cygwin guys.

I can write next tasks that need to be in MSYS mode:

1. The correct definition of executables belonging to Cygwin DLL.
2. Translating paths in arguments and environment variables to Windows
form for pure Win32 applications.
3. In MSYS mode Cygwin need to be very portable: do not use registry
to store any info, do not use /etc/passwd and /etc/group, all mount
points need to be with noacl option to avoid problems with permission
denied.
4. Ability to change OSNAME that controlled by uname function in Cygwin DLL.
5. Use shorted mount point options in /etc/fstab - only win32_path and
posix_path.
6. SYMLINKS. Now Cygwin can work with native symlinks but it cannot be
used in all situations. From the other side - Win32 applications
doesn't understand Cygwin symlinks. As fallback option we need to
create copies of files and directories instead symlinks.

I want to hear your opinions about how it can be implemented in Cygwin codebase.

Regards,
Alexey.

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