Result for D5C603902A997E93F9C48642E7C9A99777393D08

Query result

Key Value
FileName./usr/lib64/libcogl-path.so.20.4.2
FileSize79160
MD5C4FC467F2A3577422B22F38049FB6B5F
SHA-1D5C603902A997E93F9C48642E7C9A99777393D08
SHA-256E96B5429F9B9169B9846990B68C81E77ABD780B5CDFDF9F52A8FA7DDB7F18720
SSDEEP1536:q3wVge5CZXdzeJnFKi1Q4P7ukMRkrajey:q3wVv5CZXdzgXKz4SL
TLSHT10E734A0A31B2447DC0959534F99BE8A65A383810A7656F3B75C87B381E13E30AF9FD39
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
MD53ACEA62DED69CC16B68701F4E545D5D6
PackageArchx86_64
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>
PackageNamelib64cogl20
PackageRelease1.mga7
PackageVersion1.22.4
SHA-18F0C496F6FA872F6D96E2D7AB00DD2CD7A6C18CD
SHA-2562EAAC9C0E05A225C9770A2B338F051E393EAFA64BEDF8E512E926BB50691EEA5