Result for CB8F51E979A5325C7BCBEE50A52DA06E1853E697

Query result

Key Value
FileName./usr/share/doc/liberis-doc/changelog.Debian.gz
FileSize3358
MD5156B296A51470FBF1BF891217FE87A99
SHA-1CB8F51E979A5325C7BCBEE50A52DA06E1853E697
SHA-25613C94FFFE3DB769F042F4613A1EBAEA93C111717AA06DABB7B632043B0D7E6DF
SSDEEP96:Z5oJdOSZVgVx9+ioK7RH4jF7mo+KopCiP+Y4:ZQXgrNRYt+Z+n
TLSHT1E9615C73C6E94F02D84189BB7B0F355BA9595CB3D7C2691208620F01C1629661C92B76
hashlookup:parent-total21
hashlookup:trust100

Network graph view

Parents (Total: 21)

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

Key Value
FileSize251730
MD5C99C56831BE962774CB4A87CCD50BE8D
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-21
PackageSectionlibs
PackageVersion1.3.23-5
SHA-10C965657ED8785906E5A80F1A0F392C4EC23E35E
SHA-25675DDD9732A7DB8CD07BD396F3CE8C6C382759CA78277944AD695C14CA9D2E284
Key Value
FileSize104272
MD5212A8685CEF825BA8C1B9C6C35E403CB
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.23-5
SHA-11F0A9F21D6816FCA15F3780F71C0031EAA08191C
SHA-256DC07C888CF686D36A2FEE797B9B5F72D56752B5541CA8C2D59141032EED66F08
Key Value
FileSize328106
MD5D0D9A7E89331294202D51E1C0F81F9C4
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.23-5
SHA-1295028AA16F1DE11E1F7E0D1511CEA787A67843E
SHA-2561E44B0656BC54BD2E375B5F1BA343C7B2987B6DE4F2020DF955B0C8608E633F6
Key Value
FileSize104274
MD56BA2F37F3220D309DDAB8A80BE2AAFC4
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.23-5
SHA-14B542D8BF8A95A9C4B91499EF5EBA032E3903C37
SHA-256CD06DAA5B4661DF7B78EE54819CF320215174D40D33BCD724BAB1CF18D3065B2
Key Value
FileSize104266
MD58EA750609A79A638CEF1269335688712
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.23-5
SHA-157B21456F58DBF7C5C8E0F0272391F027B1A9A33
SHA-256E4CD2CC7E623B5738B041472079C6B97595038BE85BEE6465E853143F3B4E02E
Key Value
FileSize104278
MD584C4C95A3EA0DD4E494A57D8C13C4D4E
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.23-5
SHA-166419B5D9AC777D92AA61D502FDB08C9062C3A8C
SHA-256ACC4C86C2225368468E4959329F98831E823F873A24E5EE15401A020F64E4251
Key Value
FileSize279222
MD5F5AA07CE56C7931C8B11BEF284C6D600
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-21
PackageSectionlibs
PackageVersion1.3.23-5
SHA-17D9A501C6CE884AEB2520586E3C9E626C90A7CF5
SHA-256AD57D40343284C12D233CD186380B5B02DEFEC4CA32810D12365B1657741AC59
Key Value
FileSize266480
MD5519921AE54A728C6D5AED58D20BA0BC0
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-21
PackageSectionlibs
PackageVersion1.3.23-5
SHA-18656E23840939D700AB5E2C4627A137B60232BE2
SHA-256F5F8A117FD8128CBB6D446CFFB355D150BC36E4421CCE11095F2E2EF2DE4CD25
Key Value
FileSize104270
MD5A9559BF271DEEB9DC9623E7F2E568E90
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.23-5
SHA-189A338ACD77EC84AC40A5A61AB004C5715545040
SHA-256339E43132DA826BE89E69BC8708B818FEF35535442C52BF02737FA400790ED09
Key Value
FileSize262020
MD524D82F0283BC49C5CB518FB78EA57CE6
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-21
PackageSectionlibs
PackageVersion1.3.23-5
SHA-18FF6EFC4D879C886EBD1420E67D6F82492B208BE
SHA-256B6FD279AE5CD2EDF9BD581AF6A572BD9CE5DE9EDCC49E4DF881C29AD74046058