Message-ID: <55160.71.212.121.55.1234471912.squirrel@webmail.efn.org>
In-Reply-To: <4994679D.9070300@gmail.com>
References: <d508790c0902120825o10428e3bj40b582cebbbf277e@mail.gmail.com>     <4994679D.9070300@gmail.com>
Date: Thu, 12 Feb 2009 12:51:52 -0800 (PST)
Subject: Re: CygWine 1.0 Beta -- an new cygwin package manager
From: "Yitzchak Scott-Thoennes" <sthoenna@efn.org>
To: cygwin@cygwin.com
User-Agent: SquirrelMail/1.5.1
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

I'd rather see the common code put into a library (and available in
both cygwin and mingw flavors).  Then it would be pretty easy to
have a Cygwin::Setup perl extension and command line tools using it.
(Substitute your other glue language of choice as desired.)

On Thu, February 12, 2009 10:17 am, Dave Korn wrote:
> I'm taking a quick browse through the code.  I see that you've based it
> on chunks of the core setup.exe code, somewhat refactored and
> restructured.  I wonder if we couldn't merge the two codebases, in such a
> way that there's one common 'setup engine' with a couple of alternative
> GUI front-ends; that might
> be a neat way to fix up all the missing features and make sure there is
> thoroughly consistent behaviour between the two different installers.


--
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/