The package I have developed comes with a set of config files. However I want other devs to be able to add their own, not just configure the default ones.
However, now that I have tried publishing my package to packagist and installing it as a vendor package via composer, it seems that Laravel will ignore config files unless the same file name existed in the original vendor package! This is true even if I explicitly do
Config::get('{package-name}::{file-name}')
Only if that file name exists in the original workbench package does Laravel seem to allow devs to access it.
Was able to solve this with namespaces for my package config:
Config::addNamespace('package', __DIR__.'/path/to/config');
See here for info: http://laravel.com/docs/packages#package-configuration