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 Date: Fri, 11 Jan 2002 11:53:16 +0100 From: Corinna Vinschen To: cygwin-apps AT sources DOT redhat DOT com Subject: Re: new policy for packages Message-ID: <20020111115316.Y12057@cygbert.vinschen.de> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: Corinna Vinschen , cygwin-apps AT sources DOT redhat DOT com References: <079301c19a87$404969a0$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i On Fri, Jan 11, 2002 at 04:43:28AM -0600, Gary R. Van Sickle wrote: > > -----Original Message----- > > From: cygwin-apps-owner AT cygwin DOT com > > [mailto:cygwin-apps-owner AT cygwin DOT com]On Behalf Of Robert Collins > > > > I want to suggest that the following become policy: > > > > No new packages are accepted that require non-packaged prerequisites. > > > > i.e. using rpm which was raised on cygwin@ recently, > > until db 3.2 is packaged and maintained by 'someone', rpm is not > > acceptable as a package. > > > > Thoughts? > > I don't know how things could work any other way, in cases such as this anyway. postgreSQL needs cygipc. Luckily it's not a *new* packahge :) Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc.