Result for 303D5B21A28AB34DCE577E9A92A2718C486B3A8B

Query result

Key Value
FileName./usr/lib/libcogl-pango.so.20.4.3
FileSize27976
MD5C666D78EEC5C167DE080E04979ACCB73
SHA-1303D5B21A28AB34DCE577E9A92A2718C486B3A8B
SHA-2567EE2DA92D13DE2D1C1CA8697D8AD103A938E93A16475AB7715E0684CC188540B
SSDEEP384:Zz4sZdUskQqu2F4Fn9pP3JNpFzB8xLegXvCETqgGxYVDQ6a:qvgqu2FA9x3JNphBmLVvCE7kYVM6
TLSHT18DC2EAC7AC02A853C4C606FA755AEE8A72524298C1CC2F5F870C726421977AF5DBFF46
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
MD55D27770DE08713AB7B99D588BF431840
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.
PackageMaintainerakien <akien>
PackageNamelibcogl-pango20
PackageRelease3.mga8
PackageVersion1.22.8
SHA-138DF877DEE1E14CE3171A43B5D3B261EB83BAC30
SHA-25630047CAE0F8714FF21F694FA40B5CBDC61090219E95735C8738F7901CD9E64AE