A PEAR Channel or inclusion in pecl.php.net

[helgi]

It would be great if you could publishes releases via a pear channel so tools like the PEAR install (pecl install phpredis) and Pyrus (next gen of the PEAR installer, still in development) can install and manage the extension.

http://www.pirum-project.org/ could get you up and running real quick - pear.zero.mq is an example of pecl packages hosted externally. All the files generated are static so in theory you should be able to run the channel directly from github but I have never tried it... I know running it directly from SVN does work.

The other alternative which would also be nice it to get the package accepted into pecl.php.net :-)

[nicolasff]

Hi,

I actually have an account, and I should do this. This was discussed with Pierre Joye on the PECL mailing-list, and I made the few changes that he suggested in order for the package to be accepted.

Thanks for reminding me, I'll take a look very soon.

[helgi]

Any news on this? :-)

[cofyc]

hi, when will phpredis be released via pecl channel?

[mwillbanks]

Yes - really looking for this to be added into pecl; any updates there? it would also be nice because then it can go through the php bug tracker and documentation could easily be added to the php.net website.

[mostlygeek]

Hi, also interested in this :) please let us know when it is available via Pecl.

[nfarring]

Also interested in having phpredis available for installation either in pecl.php.net or a custom pirum PEAR channel. This would make it easier to integrate into the Composer/Packagist system. I switched my PHP library from phpredis to predis because of this packaging/installation problem, but would love to use phpredis instead because of the better performance. :-)

[mwillbanks]

Any updates?

[marzizzle]

Hi, I'm also interested in this

[shockie]

+1

[drewish]

I'd love to be able to use pecl to install this. Oh and please ignore mwillbanks's suggestion to use the php bug tracker. I'd rather chew broken glass than deal with that again.

[drewish]

Turns out I'd actually started a branch for putting this into a pecl package 2-years ago. I'm pretty sure I'd discussed it with Nicolas in the old owlient repo's issues but they seem to have been turned off.

So I started dusting it off to get a build-able copy and realized that I needed to drop the igbinary sub-extension and just add it as a dependency.

I think I'm going to package this up on my fork so we can use it internally and once it looks good I'll submit a pull request. I think it'll probably mean that the Debian and rpm stuff will also need work since they should probably be switched to use pecl.

[drewish]

If people want to test this out it's in my fork: https://github.com/drewish/phpredis/tree/pecl

sudo pecl install https://github.com/downloads/drewish/phpredis/PhpRedis-2.2.1.tgz

[michael-grunder]

Nice job. pecl install would be cool for sure. I'm sure we can figure out a way to merge this in somehow. Honestly I'm not very familiar with how that stuff works. :)

[drewish]

I think the real thing to having longevity with this is getting the channel setup. I'm working on getting it going on my fork using these directions:
http://blog.shupp.org/2010/12/24/github-pages-pirum-easy-pear-channel/
http://blog.stuartherbert.com/php/2011/09/22/php-components-publishing-your-pear-channel-on-github/
So once I get it all going and can document the process of adding releases to the channel I'll do a pull request.

[drewish]

The process I used to build: http://drewish.github.com/phpredis/

Install prium:

pear channel-discover pear.pirum-project.org
pear install pirum/Pirum

Create a pages repo. I did this as a separate checkout in a sibling directory:

git clone git@github.com:drewish/phpredis.git phpredis-channel
cd phpredis-channel
git checkout --orphan gh-pages
git rm -rf .

Configure the pirum.xml file then build the channel:

pirum build .

Add your channel to pear/pecl (this also validates it and warns you of any
problems before you push it up to github):

pecl channel-add channel.xml 

If that looks good then add all files and push it:

git add -A
git commit -m "Created the channel."
git push origin gh-pages

Hop up a directory (since I've got them as siblings):

cd ..

Package up a release:

pecl package phpredis/package.xml 

Switch into the pages repo:

cd phpredis-channel

Add the release in the parent directory to the channel:

pirum add . ../PhpRedis-2.2.1.tgz

If that doesn't have any errors then commit the changes and push them:

git add -A
git commit -m "Adding the PhpRedis-2.2.1 release."
git push origin gh-pages