/usr/share/perl5/Path/FindDev.pm is in libpath-finddev-perl 0.5.2-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 | use 5.008; # utf8
use strict;
use warnings;
use utf8;
package Path::FindDev;
our $VERSION = '0.5.2';
# ABSTRACT: Find a development path somewhere in an upper hierarchy.
our $AUTHORITY = 'cpan:KENTNL'; # AUTHORITY
use Sub::Exporter -setup => { exports => [ find_dev => \&_build_find_dev, ] };
sub _build_find_dev {
my ( undef, undef, $arg ) = @_;
my $finddev_object;
return sub {
my ($path) = @_;
$finddev_object ||= do {
require Path::FindDev::Object;
Path::FindDev::Object->new($arg);
};
return $finddev_object->find_dev($path);
};
}
*find_dev = _build_find_dev( __PACKAGE__, 'find_dev', {} );
1;
__END__
=pod
=encoding UTF-8
=head1 NAME
Path::FindDev - Find a development path somewhere in an upper hierarchy.
=head1 VERSION
version 0.5.2
=head1 DESCRIPTION
This package is mostly a glue layer around L<< C<Path::IsDev>|Path::IsDev >>
with a few directory walking tricks.
use Path::FindDev qw( find_dev );
if ( my $root = find_dev('/some/path/to/something/somewhere')) {
print "development root = $root";
} else {
print "No development root :(";
}
=head1 FUNCTIONS
=head2 find_dev
my $result = find_dev('/some/path');
If a C<dev> directory is found at, or above, C</some/path>, it will be returned
as a L<< C<Path::Tiny>|Path::Tiny >>
If you pass configurations to import:
use Path::FindDev find_dev => { set => $someset };
Then the exported C<find_dev> will pass that set name to L<< C<Path::IsDev>|Path::IsDev >>.
Though you should only do this if
=over 4
=item * the default set is inadequate for your usage
=item * you don't want the set to be overridden by C<%ENV>
=back
Additionally, you can call find_dev directly:
require Path::FindDev;
my $result = Path::FindDev::find_dev('/some/path');
Which by design inhibits your capacity to specify an alternative set in code.
=begin MetaPOD::JSON v1.1.0
{
"namespace":"Path::FindDev",
"interface":"exporter"
}
=end MetaPOD::JSON
=head1 EXAMPLE USE-CASES
Have you ever found yourself doing
use FindBin;
use lib "$FindBin::Bin/../../../tlib"
In a test?
Have you found yourself paranoid of file-system semantics and tried
use FindBin;
use Path::Tiny qw(path)
use lib path($FindBin::Bin)->parent->parent->parent->child('tlib')->stringify;
Have you ever done either of the above in a test, only to
find you've needed to move the test to a deeper hierarchy,
and thus, need to re-write all your path resolution?
Have you ever had this problem for multiple files?
No more!
use FindBin;
use Path::FindDev qw(find_dev);
use lib find_dev($FindBin::Bin)->child('t','tlib')->stringify;
^ Should work, regardless of which test you put it in, and regardless
of what C<$CWD> happens to be when you call it.
=head1 AUTHOR
Kent Fredric <kentfredric@gmail.com>
=head1 COPYRIGHT AND LICENSE
This software is copyright (c) 2014 by Kent Fredric <kentfredric@gmail.com>.
This is free software; you can redistribute it and/or modify it under
the same terms as the Perl 5 programming language system itself.
=cut
|