Suggest, rather than require, other libraries.

[samwilson]

These three libraries are not all required when using the Storage module, so this makes that explicit and means they aren't forced to be installed.

[morgan]

Do you know an efficient way of having composer install suggestions? I had looked at suggest and ultimately went with require because it was the most straight forward way of allowing folks to get started. If there is a way to document implementing via "suggest", I'm certainly open to it. At this point, suggest appears to be purely informational. https://getcomposer.org/doc/04-schema.md#suggest

[samwilson]

No, I'm not sure there is any way other than adding the suggestion to the main project's composer.json.

The reason I came up against this was that dev-working isn't seen as stable and so wouldn't install. But then I realised that I didn't even need it, and so suggested this fix. The other way I guess would be to create a 'comparable alias' for the dev-working branch, maybe inline: https://getcomposer.org/doc/articles/aliases.md#require-inline-alias ? I'm not really sure!

Thanks. :)

[morgan]

Ah, must be due to your minimum-stability setting as I don't have an issue. https://getcomposer.org/doc/04-schema.md#minimum-stability

This Kohana branch, 3.3/develop, is currently in the works anyway. I'll look at the options. As always, want to reduce any unnecessary complexity.

Thank you for your contribution and reaching out!