Result for 32C0E68BD30748B0E4C6DF30C5D2FF3193D71539

Query result

Key Value
FileName./usr/share/doc/liberis-1.3-19/NEWS.gz
FileSize1468
MD5D4C56DE508C795CFBAEBA8EB69B6625F
SHA-132C0E68BD30748B0E4C6DF30C5D2FF3193D71539
SHA-25666E1679CB57DD025959EAB3893F1A16F307FCC05828AF5F73E75EF308B75D866
SSDEEP24:XRjALqEjfOD/+2J2YfRSvLvQmG6tgF1iiejmN6jkKHg7c05WhTUJOsS:X9IqET4/+bcm3tgjixmNmkORTyYsS
TLSHT1A631A7E8165497747161BE782BFF0543BE891CC2AA42B0B17A2B475172DB56918381FC
hashlookup:parent-total16
hashlookup:trust100

Network graph view

Parents (Total: 16)

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

Key Value
FileSize213322
MD5A702F9B4544A5433F428C4E62615765B
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-19
PackageSectionlibs
PackageVersion1.3.19-5
SHA-1084F6C8B9B339018B3F470F8144DAF7AF06E02A4
SHA-256AE76DEFB3602B872740C19B5B5A370A9FE3C310C1F33F721EB6E1D9AE3AA9FFB
Key Value
FileSize226610
MD539A1FF964C9317892801A135215A01AC
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-20
PackageSectionlibs
PackageVersion1.3.21-0.1
SHA-117B359EFE1C8F345F1E5D0FEED7AAFC36BFACA76
SHA-256BD7ED5E75D6656A32EF1DA62E45AFAC44F2F8375A475BDAE0EF09E6ADE8DDAFB
Key Value
FileSize233308
MD523147D79DE031667CBD9A12BCC36917E
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-19
PackageSectionlibs
PackageVersion1.3.19-5
SHA-11C4B017B7B9730E33A69F49EE27461277B2A7D84
SHA-2569F07C9EC971625EA8567D12873BBCE2E377914A723C097B4F7414C299DD46EF5
Key Value
FileSize224720
MD5C4E7651AF49DCAB8F061030BEB04F956
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-20
PackageSectionlibs
PackageVersion1.3.21-0.1
SHA-1368346BAFAC530F0A7E522FE204550C3817C40C0
SHA-256FA7065AADA2ADB238BDD9D4A213A5C80F9E286BCF47974A8252D159EE48047B5
Key Value
FileSize237838
MD5D944F5B84F1D950855614AE1E01452E8
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-19
PackageSectionlibs
PackageVersion1.3.19-5ubuntu2
SHA-13B647F6FC92D8A2B19E24BFFB378F4755DCEA1BB
SHA-256DFEFBC35EB12EF36905B9497721074CB872E240E3F0A3CD80DA736A2A5D6430F
Key Value
FileSize250916
MD5138CAAC5DED7190625D2FE6BC8CCFA9D
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-20
PackageSectionlibs
PackageVersion1.3.21-0.1
SHA-14E62C867CAEB000778E86B8027BBFD4D9CBB5E7B
SHA-256432287BD939A5D4D2FD1DABA7CD54358BABFAA156CA794D5464DDF42C09DE06C
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
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
FileSize191550
MD5581D88D7294AE8E7418896D5FE869539
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-19
PackageSectionlibs
PackageVersion1.3.19-5
SHA-16F77E83964C8456D2F899B359E03088970F5D688
SHA-2560E3A396342F217B85F30A26377DD5C0A5D4E2583818BEBFA319307AE7CE29AA9
Key Value
FileSize249250
MD52FB6E5DCCDDB27F57438CBB230DE07EC
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-20
PackageSectionlibs
PackageVersion1.3.21-0.1
SHA-191EE293977A119C1548E34FCFA25CFB78802C7A9
SHA-2560BBB68956B7A169823F3DC6773F28F728DFEC81D9113D0EF2748E45AEDEC30EE