delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2009/02/12/13:30:12

X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4994679D.9070300@gmail.com>
Date: Thu, 12 Feb 2009 18:17:01 +0000
From: Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: CygWine 1.0 Beta -- an new cygwin package manager
References: <d508790c0902120825o10428e3bj40b582cebbbf277e AT mail DOT gmail DOT com>
In-Reply-To: <d508790c0902120825o10428e3bj40b582cebbbf277e@mail.gmail.com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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

Brant Young wrote:
> Hi everyone,
> 
> I have launched a opensource project -- CygWine ( a cygwin package
> management utility, project homepage: http://cygwine.googlecode.com )
> 
> CygWine 1.0 beta was just released, you can download the executable
> and browse screenshots at http://cygwine.googlecode.com.
> 
> Compared to cygwin official install tool -- setup.exe, CygWine is more
> easy to use, has more intuitive UI.

  I like the nice wx-based GUI, that's really pretty.

> Currently, some of setup.exe features not supported by CygWine, I will
> add more functions in the next release.
> 
> I hope you will like it, suggestions and contributions are welcome.

  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.  You
know your own code better than I do - do you think that would be practical?

    cheers,
      DaveK


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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019