Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Date: Fri, 11 Jan 2002 12:30:16 +0100
From: "Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>
X-Mailer: The Bat! (v1.53t) Business
Reply-To: "Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>
Organization: convey Information Systems GmbH
X-Priority: 3 (Normal)
Message-ID: <3993244037.20020111123016@familiehaase.de>
To: cygwin-apps AT sources DOT redhat DOT com
Subject: Re: new policy for packages
In-Reply-To: <079301c19a87$404969a0$0200a8c0@lifelesswks>
References: <079301c19a87$404969a0$0200a8c0 AT lifelesswks>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

 Robert,

2002-01-11 11:35:51, du schriebst:

> I want to suggest that the following become policy:

> No new packages are accepted that require non-packaged prerequisites.
[...]
> Thoughts?

Runtime only prerequisites?

e.g. in rpm-4 there are db sources included in the source package which
are statically linked in.

I think this is really obvious.  If I want to include a package which
needs a dynamic version of db and the people are not able to fetch an
official port then I will go on and build this needed db too.

But to avoid discussions it should be mentioned at the guidelines.


Gerrit
-- 
=^..^=