Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <012401c1893a$a6dd6440$0200a8c0@lifelesswks> From: "Robert Collins" To: "Charles Wilson" , Cc: References: <4 DOT 3 DOT 1 DOT 2 DOT 20011219103326 DOT 0166d180 AT pop DOT ma DOT ultranet DOT com> <3C20BBD0 DOT 3030502 AT ece DOT gatech DOT edu> <200112200844 DOT fBK8iQx13965 AT www1 DOT translationforge> <3C21A9B6 DOT 30702 AT ece DOT gatech DOT edu> Subject: Re: RPM 4 under cygwin Date: Thu, 20 Dec 2001 20:42:33 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 20 Dec 2001 09:43:05.0389 (UTC) FILETIME=[B95A35D0:01C1893A] ----- Original Message ----- From: "Charles Wilson" > No, actually you are wrong -- this is not a demonstration of anything of > the sort. Let us suppose that you COULD link cygwin1.dll statically > (into rpm.exe?). What mount table would be available for that > cygwin-inside-rpm.exe to use? As long as no absolute, non /cygdrive/ path access occurs, a static linked cygwin1.dll would be sufficient for setup.exe. However other issues still exist and I share your distate of the arrogant manner in which the question?/statement?/whatever it was was communicated to us. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/