[pkg-php-pear] Data in pear-channels/pkg-php-tool (Was: Comments regarding phpunit-mock-object)
math.parent at gmail.com
Wed Feb 5 16:34:49 UTC 2014
2014-02-05 16:22 GMT+01:00 David Prévot <david at tilapin.org>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> Le 05/02/2014 09:55, Prach Pongpanich a écrit :
>> On Wed, Feb 5, 2014 at 6:05 PM, Mathieu Parent <math.parent at gmail.com> wrote:
>>> 2014-02-04 22:09 GMT+01:00 "David Prévot" <david at tilapin.org>:
>>>> I pushed the content of debian/pkg-php-tools-overrides into pear-channels,
>>>> so we can get rid of this file once the next version of pear-channels will
>>>> be uploaded (I believe having all of them in a central place is worth it,
>>>> do not hesitate to commit any further overrides in the pear-channels
>>> Why not move this to pkg-php-tools package? There may be cases where
>>> pear-channels is not installed.
> Is there (m)any practical issues? AFAICT, overrides are mostly (only?)
> used in PEAR packages provided by third party channels (i.e., packages
> that may need pear-channels among their dependencies).
The practical issue would be if someone is using "pear
channel-discover" locally. This is minor.
>> When do we need to override the package name, we should upload the
>> pkg-php-tools without any improvement?
> I like to see pear-channels as a dumb data-only package: dumb as a
> really short amount of code (in debian/rules only) that should not need
> any edition on upgrade, and thus should not scare anyone to add data and
> upload. It also doesn’t bring much in (build-)dependencies.
> pkg-php-tool on the other hand looks like the clever engine, the code
> that build stuff, and that one wouldn’t want to break. Uploading
> pkg-php-tool should not be taken lightly, and people might get spooked
> when changing stuff there (I know I am).
> Therefore I believe pear-channels is the right place to add this kind of
> data, and if we see fit, we could even add it among pkg-php-tools
> dependencies to make sure those data will always be available when one
> use pkg-php-tools.
Why not. What people here think about having pkg-php-tools depending
More information about the pkg-php-pear