Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <06fc01c16e2d$7169d730$0200a8c0@lifelesswks> From: "Robert Collins" To: "Stipe Tolj" Cc: "Corinna Vinschen" References: <007f01c16cde$5016de20$0200a8c0@lifelesswks> <20011114124323.C24614@cygbert.vinschen.de> <3BF44A45.9DA8A866@wapme-systems.de> <06bc01c16e2a$a7061500$0200a8c0@lifelesswks> <3BF44EFA.E5ABCA5B@wapme-systems.de> Subject: Re: no more package moratorium? Date: Fri, 16 Nov 2001 10:29:58 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 15 Nov 2001 23:28:08.0435 (UTC) FILETIME=[2F025430:01C16E2D] ----- Original Message ----- From: "Stipe Tolj" > > why? if the metadata is held in a database and all setup.hints are > generated out of it we have no problems about consistence?! We've had that - setup.ini was the database, and updating was a PITA, because it couldn't be easily distributed. Setup.hint allows the metadata to be altered by the maintainer - without needing a central repository. Also, federating a database is _hard_. Federating package metadata by associating it with the packages is trivial. I've no objection to you generating a database from the package metadata, but it *must* be that way around. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/