From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20260 invoked by alias); 21 Jan 2013 19:32:31 -0000 Received: (qmail 20244 invoked by uid 22791); 21 Jan 2013 19:32:29 -0000 X-SWARE-Spam-Status: No, hits=-3.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_GT X-Spam-Check-By: sourceware.org Received: from mail-oa0-f52.google.com (HELO mail-oa0-f52.google.com) (209.85.219.52) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 21 Jan 2013 19:32:23 +0000 Received: by mail-oa0-f52.google.com with SMTP id o6so6529733oag.11 for ; Mon, 21 Jan 2013 11:32:23 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.60.5.231 with SMTP id v7mr14748940oev.62.1358796742859; Mon, 21 Jan 2013 11:32:22 -0800 (PST) Received: by 10.182.92.72 with HTTP; Mon, 21 Jan 2013 11:32:22 -0800 (PST) In-Reply-To: <20130121160057.GB9341@ednor.casa.cgf.cx> References: <20130118210944.GA519@ednor.casa.cgf.cx> <87libpd3hq.fsf@Rainer.invalid> <20130119171807.GA17812@ednor.casa.cgf.cx> <87fw1wdhng.fsf@Rainer.invalid> <20130119212028.GA17644@ednor.casa.cgf.cx> <20130120065309.GB17644@ednor.casa.cgf.cx> <20130121073228.GA8270@ednor.casa.cgf.cx> <20130121160057.GB9341@ednor.casa.cgf.cx> Date: Mon, 21 Jan 2013 19:32:00 -0000 Message-ID: Subject: Re: [PATCH] setup.exe From: green fox To: cygwin-apps@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2013-01/txt/msg00069.txt.bz2 Chris, language please. The problem in lack of decent package manager is something most of us here know for a long time. Hope everyone agrees on this point. Here we're just focusing to concentrate the work, refactor what key items we need, or can leave out with, re-use and such. At the same time, things must be kept running. So a workaround (for the mean time) is needed. We know that setup.exe is not enough. And as clealy noted, this setup-.ini thing is a _workaround_ We need a package manager to allow routine package management tasks to be accomplished in a single command. We need 1- a consistent user interface 2- automated package installation 3- upgrading and searching 4- package removal 5- package builder 6- lookup of package dependency 7- bootstrap cygwin to a clean env 8- generate/modify setup.ini and customize *And everyting must be script-ready* let me know if I left something out The existing and runing system does not allow one to specify a version for a given package/ example) what if package foo 3.1.6 had changed ABI, and 3.1.x (other thatn 6) restored the old ABI. if we have a dependency from bar, either A) if bar is compiled with 3.1.6 , then make sure foo is against 3.1.6 as well B) or check that foo != 3.1.6 , and double check that bar is compiled for version != 3.1.6 Version control using prev|curr|test is not the right way to do things, IMHO I hope this is clear enough example for _one_ of the many reasons why we need and write workarounds. As a side note libzypp =>Depends on mingw boost C++ gtk e2fsporg and so forth... I really like the algorithm they have, but we need it running quick, cheap, and simple. have not looked into it, but if it matches our requirements, prahaps a option. not sure yet. One of the reasons we sill have perl/awk/shell scripts to roll things out, is when things break, its not that hard to fix/patch a workaround. fox