This overlay provides ebuilds for x3 - Reunion, ebuilds for several mods and scripts for it and a very universal eclasses that are used by those ebuilds making it very easy to manage collisions and thus making those game' additives easy to install/uninstall using portage.

To add this overlay using layman:

1. Open layman's my-list.xml (that resides in /var/lib/layman by default) and insert the code below between the enclosing layman tags: ``` https://code.google.com/p/thexgames/" status = "unofficial" name = "thexgames">

<link>http://code.google.com/p/thexgames/</link>
<description>The X (x2, x3 mainly) related overlay (the game, addons, scripts)</description>

**2**. Now just execute $ layman -a thexgames ```

eix note:

If you're using eix, it's good time to $ eix-sync Now you can list every package of this overlay by executing $ eix --in-overlay thexgames

Features:

• break-on-block.eclass blocks the merge if there are any blocks installed and lists the packages that a user should unmerge firstly. This is a standalone eclass. If you're a developer and want to use it just call bob_bob /var/db/pkg (i suggest you to do that in any phase prior to src_unpack).
• thexgames.eclass does the magic regarding x3's cat-dats.
• tracker.eclass tracks everything the user installs.
• collisions.eclass finds the source' root, synchronizes the names of contents of the target and the additive and handles collisions.

Profit:

If you want a ebuild for some mod or script not provided by this overlay, just check any of the ebuilds it provides. Usually, all you need to do is just create a dir, cp the ebuild, rename it and just change the SRC_URI. digest it and merge. And that's all. Everything is done by the eclasses.

Final note:

I have tested this overlay for any bugs prior to uploading it. I, actually, have an overlay with test packages that do some creepy things that i don't think you will ever encounter. However, if you spotted any bugs feel free to file it here or contact me. If you are a developer, please note that some (a lot, actually :) ) of comments throughout the eclasses are obsolete as the design of every eclass has been changed a billion of times during the develop. If you have any questions, feel free to contact me.

The ultimate final note:

If you don't like it - just don't use it, seriously.

Disclaimer:

Everything provided as-is, but tested heavily for bugs and works just fine on a sane gentoo setup. Actually, all it needs is /var/db/pkg (to grep for contents, etc). If you moved it somewhere else - it will not work. Change the pDB var in tracker.eclass to fix it, genius.