X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=mPHBdmjkiYwbqDVD7RMdmzNctW9CuEOpbytxG49WT4x 3Anw5iVjTV4IUFz0XgTUBgm6cyY5EjjYLjHc/4MqBOmHQlb/UUFZRAP9jVYk+UVa HQ55TMPFCV1htHNp4ut6gdOn9ZAhLge3uBVPLiqsqIWsU4khLs4kE1aIWNByE2Qs = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=bCNGlJe8cyUBKhJJPAnSN5ZKovY=; b=fwMmNWSv2EPmxYKLB R7E4PkrorfiPEIRUYxYNvXbyFmjN3CnC72I5rVwwtOltrx2SdvNzc5K/U6x1MUZy bYY5oJltrrOCdob3PuJ+AXL/w8UuTRQXsTE6zpKyh4O3JKlGkmjmj20o/S2nCnRc ZrBr1JE9I9oIBEWJzoLaoB8ZSI= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=-4.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD autolearn=ham version=3.3.1 Message-ID: <51C0D024.7000404@etr-usa.com> Date: Tue, 18 Jun 2013 15:24:52 -0600 From: Warren Young User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Adding MSYS functionality to Cygwin References: <51C0B08E DOT 8080900 AT etr-usa DOT com> <20130618193101 DOT GB4868 AT ednor DOT casa DOT cgf DOT cx> In-Reply-To: <20130618193101.GB4868@ednor.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 6/18/2013 13:31, Christopher Faylor wrote: > On Tue, Jun 18, 2013 at 01:10:06PM -0600, Warren Young wrote: >>> 3. In MSYS mode Cygwin need to be very portable >> >> It would indeed be nice to have a portable Cygwin. That is, one that >> could be run from a copied directory or USB key, without being formally >> installed. Such a thing would need to solve the 3PP problem, though, >> which is Hard (tm). > > Why wouldn't that work now? You can copy cygwin1.dll anywhere you want. Because FAQ item 4.19, and because 3PP. I'm envisioning some configuration option (runtime or build time) that would create a cygwin1.dll that only serves the executable(s) shipped alongside it. If there is more than one executable, they would only be expected to cooperate with each other, so that the need for a common cygheap wouldn't obtain. Such a distribution wouldn't be "Cygwin" per se. Its primary purpose would be so people could bundle the DLL with a program that runs in its own little world, or a system of such programs. In this mode, Cygwin wouldn't require any persistent configuration (files on disk, the registry, etc.) or create such. It would start up in its default mode, provide whatever services the executable that loaded it required, and quietly go away again without leaving any footprints behind when unloaded. The executable linked to cygwin1p.dll ('p' = portable build variant) could make any persistent changes it wanted, of course. I'm just saying that this Portable Cygwin DLL that I have handwaved into existence shouldn't do this on its own behalf, or require that anyone else do it for the DLL ahead of time. In other words, I'm trying to turn the second 'P' in 3PP back into "Packagers". Bring the perverts back into the fold, as it were, instead of casting them out, thus giving them no reason to try and cooperate with mainline Cygwin. -- 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