Re: [PEAR-DEV] HTTP_Request2 composer include path (was Re: Can I (or Alexey) do a release of HTTP_Request2?)

> I still need to address
> http://pear.php.net/bugs/bug.php?id=20531
>
A fix for this looks like it was already merged into trunk. It's not the 
prettiest fix but should work.

> I'd also like to run some tests with composer and probably switch to
> using an autoloader and not mangling include_path.
>
> Other than these everything is indeed ready...
>
I'd like to switch o an autoloader but at least one stable composer 
release should be made with the legacy include-path option. There is a 
lot of legacy code dependent on HTTP_Request2 and getting everyone to 
update their usage to expect an autoloader is not realistic. This is an 
issue with the current stable releases on composer and one reason why 
I'd like to see a new stable release.

I propose at least the next stable release uses composer's include-path 
option.