Result for 3E0BC87D8A3AA94F2A98E5CCCFF3E9648FEF2119

Query result

Key Value
FileName./usr/lib/libcogl-path.so.20.4.2
FileSize57648
MD5B3A5E05EE5E1DA4DE2BB84BECCA3378C
SHA-13E0BC87D8A3AA94F2A98E5CCCFF3E9648FEF2119
SHA-2562DA2D53BBF6BCA594AA9FB9859EEED32345FA33183864D13D0FCCA4FD3107D7F
SSDEEP768:EHNrNbd6H3niowI3kFL4veH33c1Sd5AO6wm4CqhvGC/XS9YS72UYoC/Ln:aRddCwPLueHHkGqqhvdXERY/Ln
TLSHT1F143FA95FA024A92C7C09B36F2294B1835034FF4D4EBFB468D09572427E74FB476BA4A
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
MD5899CA221C28B886B70027BF43AC8303E
PackageArcharmv7hl
PackageDescriptionCogl is a small open source library for using 3D graphics hardware to draw pretty pictures. The API departs from the flat state machine style of OpenGL and is designed to make it easy to write orthogonal components that can render without stepping on each others toes. As well aiming for a nice API, we think having a single library as opposed to an API specification like OpenGL has a few advantages too; like being able to paper over the inconsistencies/bugs of different OpenGL implementations in a centralized place, not to mention the myriad of OpenGL extensions. It also means we are in a better position to provide utility APIs that help software developers since they only need to be implemented once and there is no risk of inconsistency between implementations. Having other backends, besides OpenGL, such as drm, Gallium or D3D are options we are interested in for the future.
PackageMaintainerovitters <ovitters>
PackageNamelibcogl20
PackageRelease1.mga7
PackageVersion1.22.4
SHA-1114CEFDA314A910125C92F01BC7E442A10D6339D
SHA-256993223FB802F7DE0906C11C281DFBF140CB1F3FAB5812FAF399147CB4D28F7A5