Result for 13957BE76B45B4EE716C8918ABFC4C3318495E0F

Query result

Key Value
FileName./usr/lib/libcogl.so.20.4.2
FileSize836668
MD5DEDBE9019B6FB659000C9EA08C5CF3DF
SHA-113957BE76B45B4EE716C8918ABFC4C3318495E0F
SHA-2565BF89303CFA7BE6C31892AB2E040CD8FDD456F5DE70A3B46638C6DD942448282
SSDEEP24576:dciy1T66tYIHu+VQXMNZGc65XHJlrTQui:SBT6Mbu+FNZGc65XHJlrTQp
TLSHT13A055C69D71B59B2F3B204F40347A2726920560AE363F2B1FF8C37A53476396AF16364
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
MD5B94146B867448771E7A7A974CF3982A7
PackageArchi586
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-1424FE1F4033F7DAD361C481543F4BA31E8D46253
SHA-2567187740117E2F4F89D23076835ACCDB7D8F266D0E6FBA78151791FCA0F961C82