Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:5826
Return-Path: <derick@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 16883 invoked by uid 1010); 30 Nov 2003 12:39:54 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 16859 invoked from network); 30 Nov 2003 12:39:53 -0000
Received: from unknown (HELO jdi.jdimedia.nl) (212.204.192.51)
  by pb1.pair.com with SMTP; 30 Nov 2003 12:39:53 -0000
Received: from [10.21.1.187] (c38047.upc-c.chello.nl [212.187.38.47])
	by jdi.jdimedia.nl (8.12.10/8.12.10) with ESMTP id hAUCdfF4016781;
	Sun, 30 Nov 2003 13:39:47 +0100
Date: Sun, 30 Nov 2003 13:39:36 +0100 (CET)
X-X-Sender: derick@localhost
To: Marcus Boerger <helly@php.net>
cc: Wez Furlong <wez@thebrainroom.com>, Jani Taskinen <sniper@iki.fi>,
        internals@lists.php.net
In-Reply-To: <166673232281.20031130133523@marcus-boerger.de>
Message-ID: <Pine.LNX.4.58.0311301337300.20884@localhost>
References: <200311300918.14257.magnus@php.net> <03f101c3b726$0f30c300$8802a8c0@obsidian>
 <Pine.LNX.4.53.0311301144150.24096@ybpnyubfg.ybpnyqbznva>
 <040201c3b726$fa681030$8802a8c0@obsidian> <Pine.LNX.4.53.0311301149070.24096@ybpnyubfg.ybpnyqbznva>
 <045201c3b728$fb554470$8802a8c0@obsidian> <166673232281.20031130133523@marcus-boerger.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Warning: helo-invalid
Subject: Re: [PHP-DEV] Move old (or non-mainstream) extensions to PECL before
 beta 3
From: derick@php.net (Derick Rethans)

On Sun, 30 Nov 2003, Marcus Boerger wrote:

> Hello Wez,
>
> Sunday, November 30, 2003, 11:01:51 AM, you wrote:
>
> > There is no point moving unmaintained code from ext to pecl;
> > its just a waste of time until we can solve the problem at
> > packaging time, which is why I'm suggesting that one of the build
> > guru's that hates these unmaintained extensions *cough* Jani
> > *cough* should work on the distro building tool which we
> > will need real soon now anyway. ;-)
>
> Why not go with RPM's then? The eays way is to split up the RPM's so that we
> can have RPMs for the basic stuff like INI, Docs and all, then for the
> different sapis and then for all the extensions. See attached makerpm for
> current state of work.

How do RPMs work on Gentoo, Debian, Windows, MacOSX...?

Derick