X-Spam-Check-By: sourceware.org
Message-ID: <448DE34F.6030303@cygwin.com>
Date: Mon, 12 Jun 2006 17:57:35 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060112 Fedora/1.5-1.fc4.remi Thunderbird/1.5 Mnenhy/0.7.4.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: RPM's require to much knowledge of setup to port easily
References: <061020062022 DOT 10945 DOT 448B29F200067FE000002AC122068246930A050E040D0C079D0A AT comcast DOT net> <448B643D DOT 6040401 AT tlinx DOT org> <Pine DOT GSO DOT 4 DOT 63 DOT 0606111355460 DOT 25353 AT access1 DOT cims DOT nyu DOT edu> <448C73CA DOT 60703 AT tlinx DOT org> <20060611203927 DOT GG12755 AT trixie DOT casa DOT cgf DOT cx> <448DC0BC DOT 10103 AT tlinx DOT org>
In-Reply-To: <448DC0BC.10103@tlinx.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 06/12/2006, Linda Walsh wrote:
> >> I still don't get all the reasons behind forcing everyone into a
> >> new format.  Is it just a power trip or what?
> >>     
> >
> > Actually, the "new" (i.e., five+ year old) format was imposed on us by
> > the Trilateral Commission.  
> ---
> Ah, but you avoided answering the question.  Why did the cygwin
> project go with another package format?  It can't be because
> rpm doesn't run natively under Win -- since when installing
> system for the first time, a non-rpm setup & install process
> is used.  "Rpm" is used after the basic packages are loaded. 

Ah, the lack of a Windows RPM port was *exactly* the reason
setup.exe was created.  The simplest way to port RPM was to use
Cygwin, which then leads to a chicken/egg problem.  In all honesty
though, if you really would like to know the details of the decision-
making process that made the install process what it is today, you
can find it all in the cygwin-apps email archives.  You'll have to
go back quite a ways to find it's beginnings though.

-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/