Prime example is drush, the Drupal Shell (http://drush.org/). The project hosts its own PEAR channel (http://pear.drush.org/). I cant seem to make the PEAR config that fpm sources to build from to grok this channel even after being bootstrapped with pear channel-X commands.
fpm always generates a new and temporary PEAR config (mainly because otherwise PEAR assumes we're running as root)
I'm happy to add flags to support different channels. Can you give me some hints on how you do this with PEAR outside of fpm? If I know how to do it, I can put it to code :)
Vendor docs on how to bootstrap the the supplemental PEAR channel proper @ http://pear.drush.org/
Oddly enough, while trying to work around, I found that hacking on default_channel and related config fields in system PEAR, with priv, never yielded a temp PEAR config with my non-defaults bits in it for fpm to use to build.
Start hacking on pear channel support (#207)
- Got closer to channel support working. When I do it manually, it
works, but through fpm it does not. Probably something silly.
(progress on #207)
Got pretty close to having this work. When I hack it manually (config-create, channel-discovery, remote-info, install) it works, but through fpm it does not - I'm probably just missing something obvious (typo, etc). Willi nvestigate soon.
- Make custom channels work with pear (#207)
- add --pear-channel-update flag to force 'pear channel-update' prior to
Looks like this is fixed.