Result for 80FCED13D4D162792DD0B16BF3E6D8F7C0C06CD3

Query result

Key Value
FileNamechangelog.Debian.gz
FileSize1377
MD526DFEA6E16EE10B88180D0A8B40C3069
RDS:package_id182052
SHA-180FCED13D4D162792DD0B16BF3E6D8F7C0C06CD3
SHA-25600DE1AB64C7A37AC4852534088174B6B0E89DC3D5D452D3231D847FEBB62AF2B
SSDEEP24:XdxXjj+RY4GfEdOj3D645D2lOQbS3Z5iauMb3oeYSFxn3gjLUBg:XddjYiEdAD64D2lOQbKZ5iCb3LYK3gT
TLSHT19421B9E261C0F47EC11AECB980A944BDF484B34CF0757041DEC5FD0585AE52C55542FE
insert-timestamp1679427784.3267632
sourceRDS.db
hashlookup:parent-total6
hashlookup:trust80

Network graph view

Parents (Total: 6)

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

Key Value
FileName16275
FileSize253484
MD57F097386CE4EEF0134630302E7468FAD
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-21
PackageSectionlibs
PackageVersion1.3.23-5
RDS:package_id182052
SHA-13BA8A46EA9D9761A11F33E98F946ABFC4817169E
SHA-256AE53B1AC0E1CD578CB0ECE7FE1A2D05478ED62D1BE98F3E78695CDBE4EA8B4DD
insert-timestamp1679408376.0656147
sourceRDS.db
Key Value
FileSize201456
MD559EE89749962459C102D13734128E688
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-21
PackageSectionlibs
PackageVersion1.3.23-5
SHA-1A1B3CD39892CA2829142666F0F0110F654ADAF76
SHA-256E4528C425FB2E62F0A2F2BC8C53098E74B3BD62B9C8F69D22923C8527FA84062
Key Value
FileSize225122
MD5C7CFBB168F6ED696A7B8370CCBD93971
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-21
PackageSectionlibs
PackageVersion1.3.23-5
SHA-158107D49B3325F0C9BB2134989C6DC5B1F081F9F
SHA-256AB52B4874030AA31A5F62FE26F19188D1B33E235712098EE24F539B68F77A827
Key Value
FileSize239232
MD557C46ACD1860D3F7EAB9A9EFC301396B
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-21
PackageSectionlibs
PackageVersion1.3.23-5
SHA-1275F871E28F57FC61ADD4A7DCB3BFB4042AF7987
SHA-256F82973A9AB31A7945D4F6109CA98EE90A0489FA5325B5A29B9FB121B10F4BE9E
Key Value
FileSize205020
MD52A679B91DE92602961D18CB47DCCA41D
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-21
PackageSectionlibs
PackageVersion1.3.23-5
SHA-189396C7FFFFF2169F712D78E0212792216BB27BD
SHA-256B78F81E25B2519A1F4E493B03E05638BDFFAD7753174248AAEE2DD659C37F64A
Key Value
FileSize205692
MD51876B814B45F98CD03512D177CEE6EC5
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-21
PackageSectionlibs
PackageVersion1.3.23-5
SHA-1A29145E1B4E145E6640BE39DC59F27C002D78B0A
SHA-25680098A7DAC99EEEC751FB590771E7A0DDD3DCC2AD4D2EB3FA52D36C460635AE9