From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7055 invoked by alias); 18 Jun 2013 18:40:42 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 7040 invoked by uid 89); 18 Jun 2013 18:40:40 -0000 X-Spam-SWARE-Status: No, score=4.0 required=5.0 tests=AWL,BAYES_00,CHARSET_FARAWAY_HEADER,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.1 Received: from mail-we0-f169.google.com (HELO mail-we0-f169.google.com) (74.125.82.169) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Tue, 18 Jun 2013 18:40:39 +0000 Received: by mail-we0-f169.google.com with SMTP id n57so3745123wev.28 for ; Tue, 18 Jun 2013 11:40:37 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.87.100 with SMTP id w4mr11557190wjz.34.1371580836975; Tue, 18 Jun 2013 11:40:36 -0700 (PDT) Received: by 10.216.11.2 with HTTP; Tue, 18 Jun 2013 11:40:36 -0700 (PDT) Date: Tue, 18 Jun 2013 18:59:00 -0000 Message-ID: Subject: Adding MSYS functionality to Cygwin From: =?KOI8-R?B?4czFy9PFyiDwwdfMz9c=?= To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 X-SW-Source: 2013-06/txt/msg00457.txt.bz2 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