X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <55160.71.212.121.55.1234471912.squirrel@webmail.efn.org> In-Reply-To: <4994679D.9070300@gmail.com> References: <4994679D DOT 9070300 AT gmail DOT 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" To: cygwin AT cygwin DOT com User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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'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/