eris 1.3.23-6 source package in Ubuntu
Changelog
eris (1.3.23-6) unstable; urgency=medium
* Fix symbols for GCC 7 update (Closes: #853391)
* Update standards to 4.1.3
- d/control: document new standards version
- d/copyright: use https in Format field
- d/watch: use https
* Update dh compat to 10
- Update d/rules
- Remove unnecessary ldconfig trigger
* Update d/copyright for ./debian directory
-- Olek Wojnar <email address hidden> Sun, 31 Dec 2017 20:59:13 -0500
Upload details
- Uploaded by:
- Debian Games Group
- Uploaded to:
- Sid
- Original maintainer:
- Debian Games Group
- Architectures:
- any all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section |
|---|
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| eris_1.3.23-6.dsc | 2.2 KiB | f418da515d2d9f92125de57b7e968e35d79e6d1c797318bd4bd3813a3d56fe98 |
| eris_1.3.23.orig.tar.xz | 402.4 KiB | 29ad7013445b8347ece9488824e66faa829574e19238af9ca4ad66b99b034555 |
| eris_1.3.23-6.debian.tar.xz | 14.6 KiB | 7b918a12374ba751c9201ad6d55741d70d664de0cfb25229aa9ca4f53d382e5e |
No changes file available.
Binary packages built by this source
- liberis-1.3-21: WorldForge 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.
- liberis-1.3-21-dbgsym: debug symbols for liberis-1.3-21
- liberis-1.3-dev: WorldForge 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.
- liberis-doc: WorldForge 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.
