Result for 10E9789E06676756A42B2506D28323DFA31CCEBC

Query result

Key Value
FileName./usr/lib/libcogl-pango.so.20.4.3
FileSize44356
MD5A993D8B41F02C3656A7CF506562AA7BC
SHA-110E9789E06676756A42B2506D28323DFA31CCEBC
SHA-2563E2F59A6C2A4BF13A2FD1F80DDED39218254CF69484E7230E5A6A22F4069C966
SSDEEP768:K6ojffTRlHCcpQUiVaQusRGB6BdLkg6SAt2Wk+yxtce07:vkftXWUiVMB0T6jb7
TLSHT1D313064AB71BDCB1F2D248B9865771229A305309D6639572FF0D772A243278CBE0A73D
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
MD53658F686D8FE7F41A3B1AED0DE2EF2DC
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.
PackageMaintainerumeabot <umeabot>
PackageNamelibcogl-pango20
PackageRelease4.mga9
PackageVersion1.22.8
SHA-1981C0E0C62DEE42A36840AA19F5753283D2C9494
SHA-2563621430B49EAB31032F975BC2DC23532FE3FD5389B5A5FB47E5806CF8AF7284D