Result for 429F1F6D5388734EED6772A36DAD7FEBF1736C04

Query result

Key Value
FileName./usr/share/doc/liberis-doc/changelog.gz
FileSize57286
MD5AC2E4C35BE1E59E830935E2230A9B6C3
SHA-1429F1F6D5388734EED6772A36DAD7FEBF1736C04
SHA-256683D5A9DB2361BE3725694F4C3713B5C1CF7974482A6EF88F215EB8D88A027D2
SSDEEP1536:60wEQvx0HlPCRG3ZD+k8V2un7hRXJsg1MINK:NZOx0HQ8pDjon7Lmm4
TLSHT1024302EAE0D3C8F5B6DE01320576336C0E952E44E1AE8294D2D44C276E6EE5C79491FB
hashlookup:parent-total61
hashlookup:trust100

Network graph view

Parents (Total: 61)

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

Key Value
FileSize104680
MD58A92C4892FFD9B6897FA18A0E6D09F87
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-8
SHA-105DD00D40D0DEF31C6F23D4EC992F38B373FE5EF
SHA-2560B3C796F047CF271C9832DF936B0B4A408B289379613A5F73174659C007667AF
Key Value
FileSize226356
MD581D0DA8BC1A5628C292250AC27FAC689
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-8
SHA-105F454429211F9CC61E8B4900EEB9312C1385C42
SHA-25600042998D9CFAF3776A71BA5E060B7A307EB40F0BCA74494AFB3110B9F93A168
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
FileSize242396
MD5017FBB92D00BF3900B33BA22EB39B428
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-8
SHA-10D6151886294087799EAD8D22F2A06A8F0B56D5D
SHA-25654AA1011C3CCAA61C77C58175C376D3AD27BEC99C5EBABE969BFE9721DE2A46F
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
FileSize260188
MD5DD4F5238E3CA28D828BAA3F4F4CECA19
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-7+b1
SHA-1209CD6F5B6382D9294E65A6890DFE29D06115C2F
SHA-256CD52001BAF7283253C80C4EB4AD129E9AFCA803BD2357324EBB311754C7B77BC
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
FileSize104680
MD59AFA05F48767018DA8DC74863B5FB8E7
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-8
SHA-12BA45C1E266FB74067C6767A128FC565C41766C8
SHA-2568F9D71FF1569883D94723A47F40152EFF22CB240A91674701DA16ADB20D70CD6
Key Value
FileSize104676
MD58CDDF70DB8456FB745CCF9E10A8FE2E7
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-8
SHA-13431CBEBA27314B570C83625CF93458A6E724F5B
SHA-256C9B50B778CBA4C55466B3D9A187DA7EF8841EF81F4B19F872A4F28A00C71505D
Key Value
FileSize281104
MD5FF21BC80CE58903343DEFFECF06984E5
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-7+b1
SHA-13741510C39D82E20B3A14573FAA212AFFD9A2608
SHA-256FBD4FD233E31FB34DB5041D6A99220F3478CB48B43DD37C722C13980554AD0E5