Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <088501c19a97$a64eb600$0200a8c0@lifelesswks> From: "Robert Collins" To: , References: <079301c19a87$404969a0$0200a8c0 AT lifelesswks> <20020111115316 DOT Y12057 AT cygbert DOT vinschen DOT de> Subject: Re: new policy for packages Date: Fri, 11 Jan 2002 23:01:05 +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: 11 Jan 2002 12:01:03.0639 (UTC) FILETIME=[A4A96A70:01C19A97] === ----- Original Message ----- From: "Corinna Vinschen" > > postgreSQL needs cygipc. > > Luckily it's not a *new* packahge :) Yes! Actually it's postgreSQL and similar that concern me: postgreSQL needs ipc, but ipc is not a package, and won't be unless the cygwin IPC looks waaay to far off (the thought being that having cygipc in will reduce motivation to 'do the right thing'). But on the other hand, we can't delay all packages that require IPC can we? So I'm mainly prompting discussion, hoping we can take what is 'common sense' now, and provide a reasonable guideline on setup.html, that most folk here will agree with. This will give a more solid answer when folk do request things - like kde/rpm/postgreSQL that have significant requirements. Rob