Parents (Total: 18)

The searched file hash is included in 18 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	C64D90B57C185A53665EFDE67267059D
PackageArch	noarch
PackageDescription	This simple module provides some handy functions to convert all those path separators automatically so filename tests will just DWIM.
PackageMaintainer	Fedora Project
PackageName	perl-Test-Filename
PackageRelease	15.fc34
PackageVersion	0.03
SHA-1	031AC3A81CE36EFAB39A24F732ACEC94691069A8
SHA-256	ED8740E7CCBABC350D7000A5BE146BE85EC93236424AC42DFFFD090726EF29F7

Key	Value
MD5	B9B239718AA2EDBF753AE907CB2A97A7
PackageArch	noarch
PackageDescription	This simple module provides some handy functions to convert all those path separators automatically so filename tests will just DWIM.
PackageMaintainer	Fedora Project
PackageName	perl-Test-Filename
PackageRelease	14.fc33
PackageVersion	0.03
SHA-1	0717CB0A48C480BCD386B60E73C99E6ADEC384B1
SHA-256	76D8AD3D746D4558FD813B8D89A31478F5523023BADBB4735E35BE0D1CFC2BAF

Key	Value
MD5	31F4D8A42A31540BBC104FB38551C502
PackageArch	noarch
PackageDescription	Many cross-platform test failures -- particularly on Win32 -- are due to hard-coded file paths being used in comparison tests. my $file = get_file(); # returns "foo\bar.t"; is( $file, "foo/bar.t" ); # fails on Win32 This simple module provides some handy functions to convert all those path separators automatically so filename tests will just DWIM. The alternative is to write your own utility subroutine and use it everywhere or just keep on littering your test code with calls to File::Spec -- yuck! is( $file, File::Spec->canonpath("some/path"), "should pass" ); Since this module is so simple, you might not think it worth including as a dependency. After all, it's not _that_ hard to always remember to use the File::Spec manpage, the Path::Tiny manpage or some other file utility, right? But odds are that, at some point, you'll be so busy writing tests that you'll forget and hard-code a path in your haste to show what a clever programmer you are. So just use this module and stop worrying about it. You'll be happier and so will anyone trying to install your modules on Win32.
PackageName	perl-Test-Filename
PackageRelease	lp151.1.1
PackageVersion	0.03
SHA-1	075525D61AD53E34CE8E667F12F6C5865C0ED5F1
SHA-256	CB5DC7041B498CC4BB54BC08FC4BE12DE2B940CAFA222D9B97A3776D0041ED37

Key	Value
FileSize	7508
MD5	01A116E7D6BE409962A3C3628C7659C3
PackageDescription	portable filename comparison Many cross-platform test failures -- particularly on Win32 -- are due to hard-coded file paths being used in comparison tests. . my $file = get_file(); # returns "foo\bar.t"; is( $file, "foo/bar.t" ); # fails on Win32 . Test::Filename provides some handy functions to convert all those path separators automatically so filename tests will just DWIM. . The alternative is to write your own utility subroutine and use it everywhere or just keep on littering your test code with calls to File::Spec -- yuck! . is( $file, File::Spec->canonpath("some/path"), "should pass" ); . Since this module is so simple, you might not think it worth including as a dependency. After all, it's not that hard to always remember to use File::Spec, Path::Tiny or some other file utility, right? But odds are that, at some point, you'll be so busy writing tests that you'll forget and hard-code a path in your haste to show what a clever programmer you are. . So just use this module and stop worrying about it. You'll be happier and so will anyone trying to install your modules on Win32.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	libtest-filename-perl
PackageSection	perl
PackageVersion	0.03-1.1
SHA-1	0AB95940D2C0F21E9F1D402B7E2079C965A3BFD5
SHA-256	188A374153350EF9B2BD24F52145EB4D9A6C6CA364A4F2B40A13E302C0AD229D

Key	Value
MD5	A5FDEC18E3D18C6D59E1FF9917988373
PackageArch	noarch
PackageDescription	Many cross-platform test failures -- particularly on Win32 -- are due to hard-coded file paths being used in comparison tests. my $file = get_file(); # returns "foo\bar.t"; is( $file, "foo/bar.t" ); # fails on Win32 This simple module provides some handy functions to convert all those path separators automatically so filename tests will just DWIM. The alternative is to write your own utility subroutine and use it everywhere or just keep on littering your test code with calls to File::Spec -- yuck! is( $file, File::Spec->canonpath("some/path"), "should pass" ); Since this module is so simple, you might not think it worth including as a dependency. After all, it's not _that_ hard to always remember to use File::Spec, Path::Tiny or some other file utility, right? But odds are that, at some point, you'll be so busy writing tests that you'll forget and hard-code a path in your haste to show what a clever programmer you are. So just use this module and stop worrying about it. You'll be happier and so will anyone trying to install your modules on Win32.
PackageName	perl-Test-Filename
PackageRelease	1.37
PackageVersion	0.03
SHA-1	33F1D461521A3F6E3825B8782EE95F5F965ABDDA
SHA-256	821D95170A0FA7463981BA104340F3FF7E78CEF9C479C2760B697113C81CDEE6

Key	Value
MD5	895086B3384FA386C9CA76A10B477B4F
PackageArch	noarch
PackageDescription	Many cross-platform test failures -- particularly on Win32 -- are due to hard-coded file paths being used in comparison tests. my $file = get_file(); # returns "foo\bar.t"; is( $file, "foo/bar.t" ); # fails on Win32 This simple module provides some handy functions to convert all those path separators automatically so filename tests will just DWIM. The alternative is to write your own utility subroutine and use it everywhere or just keep on littering your test code with calls to File::Spec -- yuck! is( $file, File::Spec->canonpath("some/path"), "should pass" ); Since this module is so simple, you might not think it worth including as a dependency. After all, it's not _that_ hard to always remember to use the File::Spec manpage, the Path::Tiny manpage or some other file utility, right? But odds are that, at some point, you'll be so busy writing tests that you'll forget and hard-code a path in your haste to show what a clever programmer you are. So just use this module and stop worrying about it. You'll be happier and so will anyone trying to install your modules on Win32.
PackageName	perl-Test-Filename
PackageRelease	lp153.1.9
PackageVersion	0.03
SHA-1	40101995260E30E0E86030F4AD2EB8964E8D448A
SHA-256	C1A538C52D07541F976184AF48E8CC9EDDE1A2B99E789F7ABA1464E9F1B646E3

Key	Value
MD5	F14BD800D2A26AF307A596D8E3FE2F2B
PackageArch	noarch
PackageDescription	Many cross-platform test failures -- particularly on Win32 -- are due to hard-coded file paths being used in comparison tests. my $file = get_file(); # returns "foo\bar.t"; is( $file, "foo/bar.t" ); # fails on Win32 This simple module provides some handy functions to convert all those path separators automatically so filename tests will just DWIM. The alternative is to write your own utility subroutine and use it everywhere or just keep on littering your test code with calls to File::Spec -- yuck! is( $file, File::Spec->canonpath("some/path"), "should pass" ); Since this module is so simple, you might not think it worth including as a dependency. After all, it's not _that_ hard to always remember to use the File::Spec manpage, the Path::Tiny manpage or some other file utility, right? But odds are that, at some point, you'll be so busy writing tests that you'll forget and hard-code a path in your haste to show what a clever programmer you are. So just use this module and stop worrying about it. You'll be happier and so will anyone trying to install your modules on Win32.
PackageName	perl-Test-Filename
PackageRelease	1.3
PackageVersion	0.03
SHA-1	42B532DD87DDF6DD47612487290362CB462D2AF5
SHA-256	6DA268EB928D6FD00B8889A012E003B48F7530AD8066DDEC6008DBED721FD6B1

Key	Value
MD5	FE0FD72A7D3BB0639DA7F9158DEF2981
PackageArch	noarch
PackageDescription	Many cross-platform test failures -- particularly on Win32 -- are due to hard-coded file paths being used in comparison tests. my $file = get_file(); # returns "foo\bar.t"; is( $file, "foo/bar.t" ); # fails on Win32 This simple module provides some handy functions to convert all those path separators automatically so filename tests will just DWIM. The alternative is to write your own utility subroutine and use it everywhere or just keep on littering your test code with calls to File::Spec -- yuck! is( $file, File::Spec->canonpath("some/path"), "should pass" ); Since this module is so simple, you might not think it worth including as a dependency. After all, it's not _that_ hard to always remember to use the File::Spec manpage, the Path::Tiny manpage or some other file utility, right? But odds are that, at some point, you'll be so busy writing tests that you'll forget and hard-code a path in your haste to show what a clever programmer you are. So just use this module and stop worrying about it. You'll be happier and so will anyone trying to install your modules on Win32.
PackageName	perl-Test-Filename
PackageRelease	1.1
PackageVersion	0.03
SHA-1	530CD730408FAB682EB597F6F4625BB445D80B45
SHA-256	28B41C1DAAF7D44F53D6DCCFA04B29D73C3E9361B104C544246390B6DA06697E

Key	Value
MD5	E30B4FDF336092A6E04FAC374A252D38
PackageArch	noarch
PackageDescription	Many cross-platform test failures -- particularly on Win32 -- are due to hard-coded file paths being used in comparison tests. my $file = get_file(); # returns "foo\bar.t"; is( $file, "foo/bar.t" ); # fails on Win32 This simple module provides some handy functions to convert all those path separators automatically so filename tests will just DWIM. The alternative is to write your own utility subroutine and use it everywhere or just keep on littering your test code with calls to File::Spec -- yuck! is( $file, File::Spec->canonpath("some/path"), "should pass" ); Since this module is so simple, you might not think it worth including as a dependency. After all, it's not _that_ hard to always remember to use the File::Spec manpage, the Path::Tiny manpage or some other file utility, right? But odds are that, at some point, you'll be so busy writing tests that you'll forget and hard-code a path in your haste to show what a clever programmer you are. So just use this module and stop worrying about it. You'll be happier and so will anyone trying to install your modules on Win32.
PackageName	perl-Test-Filename
PackageRelease	1.60
PackageVersion	0.03
SHA-1	75723997BC247B0DAC310D580C946C8EA9BD60A8
SHA-256	0356D9F91E6E04746B2978280B5312AD2A5D7D10FC35D035A784D324D1591ABF

Key	Value
MD5	1902F296A655B5F2E4C7A09DA6C6C94A
PackageArch	noarch
PackageDescription	Many cross-platform test failures -- particularly on Win32 -- are due to hard-coded file paths being used in comparison tests. my $file = get_file(); # returns "foo\bar.t"; is( $file, "foo/bar.t" ); # fails on Win32 This simple module provides some handy functions to convert all those path separators automatically so filename tests will just DWIM. The alternative is to write your own utility subroutine and use it everywhere or just keep on littering your test code with calls to File::Spec -- yuck! is( $file, File::Spec->canonpath("some/path"), "should pass" ); Since this module is so simple, you might not think it worth including as a dependency. After all, it's not _that_ hard to always remember to use the File::Spec manpage, the Path::Tiny manpage or some other file utility, right? But odds are that, at some point, you'll be so busy writing tests that you'll forget and hard-code a path in your haste to show what a clever programmer you are. So just use this module and stop worrying about it. You'll be happier and so will anyone trying to install your modules on Win32.
PackageName	perl-Test-Filename
PackageRelease	lp152.1.1
PackageVersion	0.03
SHA-1	A27C84409F4C5FF7DB766C4F4F55F71841A3178E
SHA-256	166330E8C942FBFAE5D50CAC996451E8749629BD2E17D334DCAD9E01F450876E