Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Sun, 1 Apr 2001 16:59:47 -0400 Message-Id: <200104012059.QAA16448@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f From: DJ Delorie To: ans AT beethoven DOT cpe DOT ku DOT ac DOT th CC: cygwin-apps AT cygwin DOT com In-reply-to: (message from Anon Sricharoenchai on Mon, 2 Apr 2001 03:11:48 +0700 (ICT)) Subject: Re: for interest: cygwin rpm on sourceforge References: > Why don't setup.exe bootstrap in the following way? > 1. install all *.dll needed to run cygwin program (especially rpm program). > 2. install the rpm program from tarball. > 3. then all other packages (in rpm version) can be installed. There's no reason why setup can't use RPM to install files, if someone wants to add RPM support to setup. A lot of people have been complaining that RPM isn't supported, yet nobody has offered to do the work. However, in your above list, if setup can do #1 then it's capable of installing all of cygwin *anyway*. Why force complexity if it isn't needed?