X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<4994679D.9070300@gmail.com>
References:	<d508790c0902120825o10428e3bj40b582cebbbf277e AT mail DOT gmail DOT com> <4994679D DOT 9070300 AT gmail DOT com>
Date:	Fri, 13 Feb 2009 12:33:42 +0800
Message-ID:	<d508790c0902122033k4189d074k9496548a16cbe79f@mail.gmail.com>
Subject:	Re: CygWine 1.0 Beta -- an new cygwin package manager
From:	Brant Young <yospaly AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

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

Yes, a lot of non-UI code were migrated from setup.exe.

> I wonder ... do you think that would be practical?

I think you made a wonderful proposal.

I'd like to see a common 'setup engine' separated from setup.exe, and
besides GUI front-ends, a console front-end is also necessary ( like
yum and apt-get in Linux, they are very convenient )

I suggest split current setup.exe to three components :

    * setup engine dll (which expose native C API, maintains package
install/remove/upgrade, dependence, download cache, notification
callbacks etc.)

    * setup console app ( just a front-end, process command line
options, main functions should implements in 'setup engine dll' )

    * setup GUI app ( GUI front-end )

Regards,

Brant

On Fri, Feb 13, 2009 at 2:17 AM, Dave Korn
<dave DOT korn DOT cygwin AT googlemail DOT com> wrote:
> 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/
>
>

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