-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
module_* #5
Comments
The problem therein is that while its easy to resolve where the ie: When you install those sharedirs with If you can propose some syntax to make this mapping possible, I'm all for it, but I'm inclined to think it would be grounds for a distinct module to prevent the guts getting too messy. |
outside of saying standard File::ShareDir location, or look in share (maybe some defined default substructure of share) , I don't have any good suggestions. It's likely I don't understand the problem well enough. Realistically this is about me not liking hardcoding the current dist in the module. |
The very best I think you'll be able to achieve automatically, is a layout such as /
/share/
/share/Some::Module::Name::Here But that seems problematic as I'd imagine not all filesystem types support A transliteration such as /
/share/
/share/Some-Module-Name-Here could work, but thats still rather wordy. I think the best I can muster is having a default of So the effective synopsis would be package Long::Name::Here;
use File::ShareDir::ProjectDistDir::Module qw( module_dir module_file );
sub _develop_share_subdir { 'longnamehere' }
...
sub bar {
my $dir = module_dir(__PACKAGE__ );
my $file = module_file( __PACKAGE__, 'config.yml' );
} |
any chance you'll be adding support for things like
module_dir
? so I could writeThe text was updated successfully, but these errors were encountered: