Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Reply-To: From: "Jimen Ching" To: Subject: Future releases and packages Date: Wed, 13 Oct 1999 11:09:10 -1000 Message-ID: <000501bf15bf$3265ea60$5265000a@jching.alii.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Hi, Are there any plans to supply packages with future releases of cygwin? Currently, each release of cygwin is like installing an entire OS. The problem with this is that it is hard to upgrade individual programs. I.e. if there's a new flex or bison, I either have to build it myself or wait for the next release of cygwin. With a package system, this problem doesn't exist. If there's a new package, I just need to install that package. And if there's a new version of the cygwin library, but none of the packages have changed, I can just install the new library. The drawback to a package system is that it requires more maintenance. I.e. packages must be tested, and the cygwin library must be binary- backwards compatible. Otherwise, the whole system must be re-installed. I'm just wondering if this has been considered? Thanks for listening. --jc -- jimen AT adtech-inc DOT com Adtech, Inc. (808) 734-3300 -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com