Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Tue, 24 Jul 2001 21:06:51 +0400 From: egor duda X-Mailer: The Bat! (v1.53 RC/4) Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <13435078840.20010724210651@logos-m.ru> To: Charles Wilson CC: cygwin AT cygwin DOT com Subject: Re: SETUP WIZARD FOR CYGWIN?XFREE86 In-Reply-To: <3B5DA52D.2020304@ece.gatech.edu> References: <001201c11440$f5acf5a0$806410ac AT local> <20010724112652 DOT G9776 AT redhat DOT com> <3B5DA52D DOT 2020304 AT ece DOT gatech DOT edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Tuesday, 24 July, 2001 Charles Wilson cwilson AT ece DOT gatech DOT edu wrote: CW> Port rpm to win32. Not cygwin. i can't see why "not cygwin". bootstrapping *is* a problem, but honestly, it seems easier to me than mingw port of rpm. cygwin1.dll is reasonably self-sufficient nowadays. i'm using "minimalistic ssh client" which consists of 3 files: cygwin1.dll, ssh.exe (from openssh) and small bat file which sets %HOME% before staring ssh. everything's working perfectly either on wnt or w9x. sure, rpm is more "system-dependent" than ssh, but anyway, i don't see a big problem to create mounts (the only (?) cygwinism rpm really needs) on the early stages of bootstrap. if you're concerned about different versions of cygwin1.dll, take a look at cygwin testsuite. there're no problems with testing new build of cygwin1.dll while several programs based on the old one are running in the same time on the same machine. Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19 -- 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/