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
Message-ID:	<08cd01c19a9a$34dc04c0$0200a8c0@lifelesswks>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>,
	<cygwin-apps AT sources DOT redhat DOT com>
References:	<079301c19a87$404969a0$0200a8c0 AT lifelesswks> <3993244037 DOT 20020111123016 AT familiehaase DOT de>
Subject:	Re: new policy for packages
Date:	Fri, 11 Jan 2002 23:19:23 +1100
MIME-Version:	1.0
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:19:21.0787 (UTC) FILETIME=[333580B0:01C19A9A]

----- Original Message -----
From: "Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>

> Runtime only prerequisites?

Essentially. Complex build time would be a concern, but not as much of
one (depending on the reputation of the packager). (i.e. long time
contributor, low risk. New contributor, might package and run :}).

> 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.

Build and contribute as a package I presume? Yes, in fact that is the
intent - to make it obvious that such will be *expected* if someone
wants to contribute a package.

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

Exactly.

Rob

- Raw text -