Result for 42526C917806FFF12FC8E08EDFFB2E6E675D5988

Query result

Key Value
FileName./usr/share/doc/liberis-1.2/changelog.Debian.gz
FileSize808
MD54AC19FF1047C6905D0B0FCE8ADA93E80
SHA-142526C917806FFF12FC8E08EDFFB2E6E675D5988
SHA-256D9DF57EFD3AC56294CFF9475D850E202C2FF868DFE9F6E3DDCEF5151841FEB29
SSDEEP24:XD+/DhzN8hnDvGHlKoPAFeo1zFdd1uojQnx8:XDUannooFeo5TuojCO
TLSHT1E00186CBD110164C6867E2E643B7512ECBEE0EC894562C5431270BB0AF86ED6083D16E
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
FileSize60472
MD58B27D322811A770AF40767EB1406E49D
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-1
SHA-1CECC37075BA91047A7C631175D495F61BE7470F4
SHA-25627C430FC7C3965CAD74F566B4C451CCFE2126AB2788E35292C432329DD8EC16A
Key Value
FileSize315114
MD53888CBB719A7CEC6BE2EC3A690247983
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.2
PackageSectionlibs
PackageVersion1.2.1-1
SHA-100754AEF62F746B89C26B2BE85B169AB0DBC4E53
SHA-2565E22D5D5D38FF10941DBD88BBCBB5CF205C3DC009B8658DA8097E364F42E4568
Key Value
FileSize2206802
MD59563D61B072AA460759651C1D8EC253D
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-1
SHA-195BA653C4A627917816532F3266882425B15E5F7
SHA-2568BAC0227819D9D844405621AD5B323AFB5A8B3C1F74C5474AD5D1FA6AEFC90C5