Result for AD75C85C99B30072221DEB756FC080FC14B81438

Query result

Key Value
FileName./usr/share/man/man3/YAML::Tiny.3pm.gz
FileSize7604
MD5E4AA4E82CA27E1084B63305AC7ABF54D
SHA-1AD75C85C99B30072221DEB756FC080FC14B81438
SHA-2565F2735570230D5A2295FA4692B17FBC715F02E0321BCFCBFC185AF346799F610
SSDEEP96:eT0wBj9XEfj0VO6XmW992jeI+KycBHolhWNgo3UnxBelKr1Vx9QXOpwKwcuhB/0E:8cWmW2jdtolMNzUqlwQOpIbyXi
TLSHT12DF19E5DF0B203EBECDEC8B518DCEDF651E924159AD129D345D785AB309C29982280F9
hashlookup:parent-total4
hashlookup:trust70

Network graph view

Parents (Total: 4)

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

Key Value
MD583B23170E1CE0BA29162BC76BEA3D225
PackageArchnoarch
PackageDescription*YAML::Tiny* is a perl class for reading and writing YAML-style files, written with as little code as possible, reducing load time and memory overhead. Most of the time it is accepted that Perl applications use a lot of memory and modules. The *::Tiny* family of modules is specifically intended to provide an ultralight and zero-dependency alternative to many more-thorough standard modules. This module is primarily for reading human-written files (like simple config files) and generating very simple human-readable files. Note that I said *human-readable* and not *geek-readable*. The sort of files that your average manager or secretary should be able to look at and make sense of. YAML::Tiny does not generate comments, it won't necessarily preserve the order of your hashes, and it will normalise if reading in and writing out again. It only supports a very basic subset of the full YAML specification. Usage is targeted at files like Perl's META.yml, for which a small and easily-embeddable module is extremely attractive. Features will only be added if they are human readable, and can be written in a few lines of code. Please don't be offended if your request is refused. Someone has to draw the line, and for YAML::Tiny that someone is me. If you need something with more power move up to YAML (7 megabytes of memory overhead) or YAML::XS (6 megabytes memory overhead and requires a C compiler). To restate, YAML::Tiny does *not* preserve your comments, whitespace, or the order of your YAML data. But it should round-trip from Perl structure to file and back again just fine.
PackageMaintainerhttps://bugs.opensuse.org
PackageNameperl-YAML-Tiny
PackageReleaselp151.2.1
PackageVersion1.70
SHA-13189BB8E708E9F000E444F868E97EDEE079739B0
SHA-25673C0E8442B3FB9E395D564BEAE7BE95522E537A7E7DD0744FAAEDFB401498400
Key Value
MD5F3C989B70534AD757BCE232F18B5F677
PackageArchnoarch
PackageDescription*YAML::Tiny* is a perl class for reading and writing YAML-style files, written with as little code as possible, reducing load time and memory overhead. Most of the time it is accepted that Perl applications use a lot of memory and modules. The *::Tiny* family of modules is specifically intended to provide an ultralight and zero-dependency alternative to many more-thorough standard modules. This module is primarily for reading human-written files (like simple config files) and generating very simple human-readable files. Note that I said *human-readable* and not *geek-readable*. The sort of files that your average manager or secretary should be able to look at and make sense of. YAML::Tiny does not generate comments, it won't necessarily preserve the order of your hashes, and it will normalise if reading in and writing out again. It only supports a very basic subset of the full YAML specification. Usage is targeted at files like Perl's META.yml, for which a small and easily-embeddable module is extremely attractive. Features will only be added if they are human readable, and can be written in a few lines of code. Please don't be offended if your request is refused. Someone has to draw the line, and for YAML::Tiny that someone is me. If you need something with more power move up to YAML (7 megabytes of memory overhead) or YAML::XS (6 megabytes memory overhead and requires a C compiler). To restate, YAML::Tiny does *not* preserve your comments, whitespace, or the order of your YAML data. But it should round-trip from Perl structure to file and back again just fine.
PackageMaintainerhttps://bugs.opensuse.org
PackageNameperl-YAML-Tiny
PackageReleaselp152.3.2
PackageVersion1.70
SHA-1D6DECCED64D8E8CCD48532AF966138C866C7442B
SHA-256D10BF65B7D7E5C40E15170207068736B2828735A8DD2F474BF49976F1D6B6D85
Key Value
MD5181586DA12D87E730DAB27DF98CEC962
PackageArchnoarch
PackageDescription*YAML::Tiny* is a perl class for reading and writing YAML-style files, written with as little code as possible, reducing load time and memory overhead. Most of the time it is accepted that Perl applications use a lot of memory and modules. The *::Tiny* family of modules is specifically intended to provide an ultralight and zero-dependency alternative to many more-thorough standard modules. This module is primarily for reading human-written files (like simple config files) and generating very simple human-readable files. Note that I said *human-readable* and not *geek-readable*. The sort of files that your average manager or secretary should be able to look at and make sense of. YAML::Tiny does not generate comments, it won't necessarily preserve the order of your hashes, and it will normalise if reading in and writing out again. It only supports a very basic subset of the full YAML specification. Usage is targeted at files like Perl's META.yml, for which a small and easily-embeddable module is extremely attractive. Features will only be added if they are human readable, and can be written in a few lines of code. Please don't be offended if your request is refused. Someone has to draw the line, and for YAML::Tiny that someone is me. If you need something with more power move up to YAML (7 megabytes of memory overhead) or YAML::XS (6 megabytes memory overhead and requires a C compiler). To restate, YAML::Tiny does *not* preserve your comments, whitespace, or the order of your YAML data. But it should round-trip from Perl structure to file and back again just fine.
PackageMaintainerhttps://www.suse.com/
PackageNameperl-YAML-Tiny
PackageRelease1.24
PackageVersion1.70
SHA-15EA6BF53874672BEDEB800CDDE9BCF3B209C7182
SHA-2567AABC7184B72A1990575A0C7916114DAA524F082DC038ACDE8EB6A0271A3A0FE
Key Value
MD5D61D67A76C46D1C3E63EE497FE7BC68C
PackageArchnoarch
PackageDescription*YAML::Tiny* is a perl class for reading and writing YAML-style files, written with as little code as possible, reducing load time and memory overhead. Most of the time it is accepted that Perl applications use a lot of memory and modules. The *::Tiny* family of modules is specifically intended to provide an ultralight and zero-dependency alternative to many more-thorough standard modules. This module is primarily for reading human-written files (like simple config files) and generating very simple human-readable files. Note that I said *human-readable* and not *geek-readable*. The sort of files that your average manager or secretary should be able to look at and make sense of. YAML::Tiny does not generate comments, it won't necessarily preserve the order of your hashes, and it will normalise if reading in and writing out again. It only supports a very basic subset of the full YAML specification. Usage is targeted at files like Perl's META.yml, for which a small and easily-embeddable module is extremely attractive. Features will only be added if they are human readable, and can be written in a few lines of code. Please don't be offended if your request is refused. Someone has to draw the line, and for YAML::Tiny that someone is me. If you need something with more power move up to YAML (7 megabytes of memory overhead) or YAML::XS (6 megabytes memory overhead and requires a C compiler). To restate, YAML::Tiny does *not* preserve your comments, whitespace, or the order of your YAML data. But it should round-trip from Perl structure to file and back again just fine.
PackageMaintainerhttps://bugs.opensuse.org
PackageNameperl-YAML-Tiny
PackageReleaselp150.1.7
PackageVersion1.70
SHA-1174A662177213F803D06D2CDB1BC72FA1BCF91DE
SHA-256EC7011AB2DA575FCD74B320EC17C1937C4CA2F5D884C952FC8BB3700C0A2A336