[pkg-php-pear] Pear channels in a single package

Mathieu Parent math.parent at gmail.com
Mon Oct 21 14:18:47 UTC 2013

2013/10/20 David Prévot <david at tilapin.org>:
> Hi,

Hi David,

> Le 20/10/2013 14:23, Mathieu Parent a écrit :
>> 2013/10/19 David Prévot <taffit at debian.org>:
>>>> Le 17/09/2013 06:41, Thomas Goirand a écrit :
>>>>> Do you agree with doing a single package with all the channels, in order
>>>>> to reduce the amounts of packages, and avoid having so many packages
>>>>> holding a tiny file?
>>> Unless I missed something, it appears nobody has started to work on this
>>> pear-channels package, right?
>> No, but ....
> Well, the game has started in #726918 and I just pushed a proposed
> updating workflow into Git (I finally opted to make it a non-native
> package):
>         http://anonscm.debian.org/gitweb/?p=pkg-php/pear-channels.git

I have seen this. This is great.

>>> Since I really begin to miss some packages that are in the NEW queue for
>>> months because of this issue, I might consider working on it ASAP
>> I prefer to avoid code duplication, and push it into pkg-php-tools.
> How do you plan to address the loop concerns raised last month?
> http://lists.alioth.debian.org/pipermail/pkg-php-pear/2013-September/001639.html

I'm not sure that this is a good idea to pull the pear channel
packages by default:
- Most of the PECL packages come from the pecl.php.net website.
- The channel list will change over time, and we'll get FTBFS between

>> It will work like this:
>> - channel.xml will be installed in the main package (usually the first)
>> - channel.$package.xml will be installed in $package
>> - channel.$package.<anything>.xml will be installed in $package
> If you plan on increasing the number of binary packages for any new
> channel, it definitely won’t address the ftpmaster’s concerns (it will
> furthermore add the hassle to pass through the NEW queue every time one
> new binary package is added).

Yes. But the <anything>makes it easy to have a single package.

> There is nothing carved in stone, but the proposed layout in
> pear-channels is to conveniently put every channel.xml file in the
> channels/ directory, following the channels/$url_to/channel.xml path.

OK. Then I won't make the change in pkg-php-tools.

> All channel registry entries shall then be installed by the single
> pear-channels binary package

> that will also conveniently install a
> shared pkg-php-tools-overrides file.

I think that all overrides should be installed from the pkg-php-tools
to avoid improper behavior.

> I’d now like to work on the building part of the package. I’m still note
> convinced that build-depending on pkg-php-tools will be the smartest
> move (because of the potential loop) — unless you actually wish to
> directly build the pear-channels binary package from the pkg-php-tools
> source package — but I’d be happily convinced otherwise.

OK to not build-depend on pkg-php-tools.



More information about the pkg-php-pear mailing list