Result for 6528F8D8107430B71318128B7774F8C32F1949C7

Query result

Key Value
FileName./usr/share/doc/liberis-1.2c2/changelog.Debian.gz
FileSize1065
MD5DFED40155E5534554A2A89E509E68F47
SHA-16528F8D8107430B71318128B7774F8C32F1949C7
SHA-2568AAACB98BA3EC5295A080C8FA5E8EE0F92C95272CA15CF24868E6F80B7A6ACC2
SSDEEP24:XZIb0XJxeseDtVRsAIzlBb/aV4Rvx7sCwKs2iBmwMJIpVf:XZrBeDnKdXbyV4T9iBHSIPf
TLSHT19511E9328CB8466F24A5232B05444CA23F4C03C1FF5EB98CCA19B04E44E51F69362924
hashlookup:parent-total3
hashlookup:trust65

Network graph view

Parents (Total: 3)

The searched file hash is included in 3 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize60754
MD5E9B778D0883410A64459635DC139D042
PackageDescriptionThe WorldForge client entity library - development files Eris is designed to simplify client development (and avoid repeating the same work several times), by providing a common system to deal with the back end tasks. Notably, Eris encapsulates most of the work in getting Atlas entities available on your client, logging into a server, and managing updates from the server. Thus it can be considered as a session layer above Atlas, providing persistent (for the session) objects as opposed to Atlas ones (which are transient). It handles the client-side implementation of the meta-server protocol, and querying game servers; out-of-game (OOG) operations (via the Lobby and Rooms), and most important in-game (IG) operations such as entity creation, movement and updates. . Eris provides a generic 'Entity' class, which you are free to sub-class and provide to the system (by registering a factory with the World); thus you are free to create different classes to handle characters, walls, vehicles, etc as your client dictates. An alternative approach is to simply create peer classes, and connect them to Eris via callbacks. Eris makes extensive use of libSigC++, which must be correctly installed and functioning on your system. Familiarity with signal/slot programming concepts is essential for using Eris; the libSigC++ home-page has some examples. Gtk+ or QT signal systems also provide a good introduction. . This package contains the development files for compiling software depending on Eris.
PackageMaintainerMichael Koch <konqueror@gmx.de>
PackageNameliberis-1.2-dev
PackageSectionlibdevel
PackageVersion1.2.1-1ubuntu4
SHA-1F3A09D693D30950B63F1EEBA07ECD1C573E9B6BB
SHA-2567A2856BA44FEB2B725D607EF3138302315B2286934B83A32DA82884A4C72526B
Key Value
FileSize1712784
MD5766AA2024BAADBA659A28AFBBEB03C43
PackageDescriptionThe WorldForge client entity library - debugging library Eris is designed to simplify client development (and avoid repeating the same work several times), by providing a common system to deal with the back end tasks. Notably, Eris encapsulates most of the work in getting Atlas entities available on your client, logging into a server, and managing updates from the server. Thus it can be considered as a session layer above Atlas, providing persistent (for the session) objects as opposed to Atlas ones (which are transient). It handles the client-side implementation of the meta-server protocol, and querying game servers; out-of-game (OOG) operations (via the Lobby and Rooms), and most important in-game (IG) operations such as entity creation, movement and updates. . Eris provides a generic 'Entity' class, which you are free to sub-class and provide to the system (by registering a factory with the World); thus you are free to create different classes to handle characters, walls, vehicles, etc as your client dictates. An alternative approach is to simply create peer classes, and connect them to Eris via callbacks. Eris makes extensive use of libSigC++, which must be correctly installed and functioning on your system. Familiarity with signal/slot programming concepts is essential for using Eris; the libSigC++ home-page has some examples. Gtk+ or QT signal systems also provide a good introduction. . This package contains the debugging library.
PackageMaintainerMichael Koch <konqueror@gmx.de>
PackageNameliberis-1.2-dbg
PackageSectionlibdevel
PackageVersion1.2.1-1ubuntu4
SHA-10115744A83CD9F2DFA8CD8C74388965C567AD7AB
SHA-2561C45009B40A19D01142295E6EB63A344E044D30767F39BBAECBEF9F29AB17A74
Key Value
FileSize374212
MD545FF942B84D84A22AFA90346641E27A4
PackageDescriptionThe WorldForge client entity library Eris is designed to simplify client development (and avoid repeating the same work several times), by providing a common system to deal with the back end tasks. Notably, Eris encapsulates most of the work in getting Atlas entities available on your client, logging into a server, and managing updates from the server. Thus it can be considered as a session layer above Atlas, providing persistent (for the session) objects as opposed to Atlas ones (which are transient). It handles the client-side implementation of the meta-server protocol, and querying game servers; out-of-game (OOG) operations (via the Lobby and Rooms), and most important in-game (IG) operations such as entity creation, movement and updates. . Eris provides a generic 'Entity' class, which you are free to sub-class and provide to the system (by registering a factory with the World); thus you are free to create different classes to handle characters, walls, vehicles, etc as your client dictates. An alternative approach is to simply create peer classes, and connect them to Eris via callbacks. Eris makes extensive use of libSigC++, which must be correctly installed and functioning on your system. Familiarity with signal/slot programming concepts is essential for using Eris; the libSigC++ home-page has some examples. Gtk+ or QT signal systems also provide a good introduction.
PackageMaintainerMichael Koch <konqueror@gmx.de>
PackageNameliberis-1.2c2
PackageSectionlibs
PackageVersion1.2.1-1ubuntu4
SHA-19932BAA5817C69DD2FEDCD87AD18D08F4496DE16
SHA-2568F1D1C0975058D0A9623D0FAD9B90FA5D7DBE85EDDE5F857A72CDEFC575A55F7