Result for 3F887A139898191112C492EC3425E0FE99B62AA9

Query result

Key Value
FileName./usr/lib/libcogl-path.so.20.4.3
FileSize61696
MD5E7AB2BEE9585740265ABC4B4B691BDE0
SHA-13F887A139898191112C492EC3425E0FE99B62AA9
SHA-25626772A0022199EA8B37B7716CA9F84E050C4BEED6F23ECB3A03608075084AA9B
SSDEEP1536:JEWJSq9X1iqam2piiKhMnDVlwx3IfqL6:JNXIB5EiKhIk3gI6
TLSHT104532B86BE128BB2CBC09731F62917183B070BB8C1EBB7428D045B6467E74FB476B559
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
MD54A5DCA18AAE584350F28A546C50EACF1
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.
PackageMaintainerumeabot <umeabot>
PackageNamelibcogl20
PackageRelease4.mga9
PackageVersion1.22.8
SHA-1A43DA35F34B6D0961D69B8A0677DB4443B264676
SHA-256D36C022EF49018D1687DEA620D278013E0E0BF52877F90C8085545BBB64B3706