Result for 662870756FC04E5EDC31729308350CB3850D9EF8

Query result

Key Value
FileName./usr/share/doc/liberis-doc/changelog.gz
FileSize55322
MD57D3D20D20E20E14D05B83183FA537157
SHA-1662870756FC04E5EDC31729308350CB3850D9EF8
SHA-2565F27974B56ACFCDA879E835A2723D05F8DA43188364788CA5F978D6A1481CBC9
SSDEEP1536:6MqKgjl+huVqsNfpRYKI53OIyEYe864jwwC:Jd6euYEpR/I53Ot/r649C
TLSHT1AE43F1700AF60E56DE7F763F2370B195A714DA2D0829C6E0561C70E79CC9ED9A3983B2
hashlookup:parent-total13
hashlookup:trust100

Network graph view

Parents (Total: 13)

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

Key Value
FileSize101142
MD5EACD93686506D77C37864CEBF233E3D3
PackageDescriptionWorldForge 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.
PackageMaintainerDebian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageNameliberis-1.3-dev
PackageSectionlibdevel
PackageVersion1.3.21-0.1
SHA-11E45144DA2C76C5EF7197D289964C007C415F751
SHA-256D7E7D88432D16C1C705571BC8453C9CBC4E353EF3B28E136EFD8196C5BF68529
Key Value
FileSize2862978
MD5A7858A03F2CA5AC21A71CDC96F6C6E7F
PackageDescriptionWorldForge 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.
PackageMaintainerDebian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageNameliberis-1.3-20-dbg
PackageSectiondebug
PackageVersion1.3.21-0.1
SHA-1248D8B9FAD5A21878458DAADD7911F8B1C385549
SHA-2564DF37E51440D28797AD952924E3D3CEB208FBDC8099F22B0B5F7AC346430000E
Key Value
FileSize2904424
MD5DB56374F3777603F80B33FEA9CA60322
PackageDescriptionWorldForge 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.
PackageMaintainerDebian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageNameliberis-1.3-20-dbg
PackageSectiondebug
PackageVersion1.3.21-0.1
SHA-1826EE110B19E358EDAE0351C496C6E0054CF5D09
SHA-25698991D7F13B2256422AA1F0C944C87F4FFB64E202CE0AFA1D163E904D01180A1
Key Value
FileSize269940
MD5FCACA59D10D23D20C77E23A7E8384970
PackageDescriptionWorldForge 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.
PackageMaintainerDebian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageNameliberis-1.3-20
PackageSectionlibs
PackageVersion1.3.21-0.1
SHA-1FD7CB40822EF415511520D76CCB3937758D6C1BA
SHA-25620C421BD11E7228433D73E6D8021AA4A93A7E5649A8E9860ECCA8B02D3F88CFA
Key Value
FileSize278038
MD5A6B5D06266A3FB0AA8B2C2DFFB1F1D2F
PackageDescriptionWorldForge client entity library - API documentation 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 API documentation in HTML format.
PackageMaintainerDebian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageNameliberis-doc
PackageSectiondoc
PackageVersion1.3.21-0.1
SHA-1CC848760B0B99F01DF7C30175C085CC787EED8AD
SHA-256BC1F68DD41BB3025C3A28DEDBF2ADB46800C6129A3393832A7B314C5D5BB66BB
Key Value
FileSize2915956
MD51ED582D153F98661E2629741DA6D2B20
PackageDescriptionWorldForge 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.
PackageMaintainerDebian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageNameliberis-1.3-20-dbg
PackageSectiondebug
PackageVersion1.3.21-0.1
SHA-1472343A2F84FE58216FFD682EBF0F97DD663ABED
SHA-25691B5877020D5D52D45CC4D3E72389349BB257FCFF2FD80782D20991D036E4AF1
Key Value
FileSize2999816
MD5D6219284BC388A7B4E6348DE1DE29032
PackageDescriptionWorldForge 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.
PackageMaintainerDebian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageNameliberis-1.3-20-dbg
PackageSectiondebug
PackageVersion1.3.21-0.1
SHA-1B97D574C26F45841EEDE355A91FE08B5617300CF
SHA-256B4FA3CCF70A33AD6119A564D1B3C11DCAB547ED0967B20198B616E2B12EE3451
Key Value
FileSize279424
MD57F0E57529D3BDDF55135B4E8E60D4078
PackageDescriptionWorldForge 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.
PackageMaintainerDebian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageNameliberis-1.3-20
PackageSectionlibs
PackageVersion1.3.21-0.1
SHA-1536E59F4A019368EDADFFB441F0C9969FE4BCB7F
SHA-25697524590E586E780DBCFDD8F699389D9DC4557D24D928804D67C8D73271C553D
Key Value
FileSize101016
MD592A3EE52727323963504C9A0314B17F1
PackageDescriptionWorldForge 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.
PackageMaintainerDebian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageNameliberis-1.3-dev
PackageSectionlibdevel
PackageVersion1.3.21-0.1
SHA-17BF114461B6F17A3A0C75703ABCF88A0B33E8645
SHA-2563125DEBDAD8184E7BD834C335D344A261F571D44BAF698C64A5293A913988644
Key Value
FileSize308040
MD53010700420A44854C130CC2A66458BEC
PackageDescriptionWorldForge 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.
PackageMaintainerDebian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageNameliberis-1.3-20
PackageSectionlibs
PackageVersion1.3.21-0.1
SHA-157BE602A18BCF3575E9EE6BB2CEC22ED128B71F8
SHA-2565054EE7CF7A4F5DA4CCC7EFBE09331536ADB673E4ED886021DBD289855C1BB9F
Key Value
FileSize310108
MD5A7828CFE4B37B1610F6B074E44D7F633
PackageDescriptionWorldForge 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.
PackageMaintainerDebian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageNameliberis-1.3-20
PackageSectionlibs
PackageVersion1.3.21-0.1
SHA-1F7CBF99FF6A83E168ED60E06F1925D47EE120F6D
SHA-256D6B64F8B8808CD66ED7F4FA03EC39321207B3AD632352BDEC7ACF59553D27D60
Key Value
FileSize101048
MD569E24FF527B53A1818A146BBCE7DF280
PackageDescriptionWorldForge 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.
PackageMaintainerDebian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageNameliberis-1.3-dev
PackageSectionlibdevel
PackageVersion1.3.21-0.1
SHA-1620FDB0A25C60CC06BE7B31F719D4ED7135340D4
SHA-25600DBC01CE94CDAF69A82770B861FE93860781F45267B27798877DC1FCA311022
Key Value
FileSize101030
MD56616007C08218DB2FD71CF884A01AE57
PackageDescriptionWorldForge 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.
PackageMaintainerDebian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageNameliberis-1.3-dev
PackageSectionlibdevel
PackageVersion1.3.21-0.1
SHA-1A3B9ED26B5CDD7E091DBAC58E4486240B788D17C
SHA-256F08F096CDB4C0BB752E824586AA1AD1CEFB84D5BA52879655696AE11254F22BA