Result for B63BE2AD1DFE9335198EBB5BC09F934703696F5E

Query result

Key Value
FileName./usr/share/doc/perl-MRO-Compat/MYMETA.yml
FileSize800
MD5C0E0117B2E9D9800B814ECF1091347C3
SHA-1B63BE2AD1DFE9335198EBB5BC09F934703696F5E
SHA-2566BDF901D890000B366089788BF13839C187FAB657889700F83DCD4BFDEB9B9F6
SSDEEP12:gFGjiKpnRPPUd+scfi0wVKDCCpBZL5eifgcqYCkAmOGOene6tN2OlBjTH0LlN:g8iw9fi9VCB15Ufk+GxlB/Hs7
TLSHT18501C9D60648DA5BA300D7837FA9B009A7725B4AFBDA0D79C0D2080941F39913BE491A
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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

Key Value
MD529C2F57C51AAB38FD02EC2AFBC9EFC7B
PackageArchnoarch
PackageDescriptionThe "mro" namespace provides several utilities for dealing with method resolution order and method caching in general in Perl 5.9.5 and higher. This upstream_name provides those interfaces for earlier versions of Perl (back to 5.6.0 anyways). It is a harmless no-op to use this upstream_name on 5.9.5+. If you're writing a piece of software that would like to use the parts of 5.9.5+'s mro:: interfaces that are supported here, and you want compatibility with older Perls, this is the upstream_name for you. Some parts of this interface will work better with Class::C3::XS installed, but it's not a requirement. This upstream_name never exports any functions. All calls must be fully qualified with the mro:: prefix. The interface documentation here serves only as a quick reference of what the function basically does, and what differences between MRO::Compat and 5.9.5+ one should look out for. The main docs in 5.9.5's mro are the real interface docs, and contain a lot of other
PackageMaintainerumeabot <umeabot>
PackageNameperl-MRO-Compat
PackageRelease2.mga9
PackageVersion0.150.0
SHA-1FE09BB3A7567487D9924C35F2638AAE9E56D2B4E
SHA-25631E157CBA2256917269CC11DE4834EF48356A47ED7618E198D6AF51EBFA1B39B