The default bin_dir is /usr/bin even when you do a local installation. When pyrus is initialized, it should use a local bin dir.
Not advocating for one way or the other, just some more info:
Changing this would make pyrus handle scripts different than PEAR. Currently the bin_dir defaults to the same directory as the php executable. This ensures commands installed will likely be in your path. It would be a little odd to install PHPUnit, and not get the phpunit command at CLI without first specifying another bin_dir directory.
Use space instead of \n for the schemaLocation list
The \XMLWriter class will convert attributes with newlines into these to
and . To work-around this issue, Pyrus\XMLWriter removes
newline characters which affects the channel.xml root attributes.
To make pyrus more usable in more locations, shared hosts for example, having a user defined bin directory option would make pyrus more portable. Keep the default, but allow users to define their own bin.
Well, it would be nice if this would be documented somewhere.
Perhaps instead add an option to the first-run install process which allows you to override the default bin (or press enter to keep /usr/bin default). This way it is very clear, each time you install (on a vhost setup).