Package Details: openxcom-extended 1:7.12.8-1

Git Clone URL: https://aur.archlinux.org/openxcom-extended.git (read-only, click to copy)
Package Base: openxcom-extended
Description: An extended version of the open-source reimplementation of X-COM (OXCE)
Upstream URL: https://openxcom.org/forum/index.php/topic,5251.0.html
Licenses: GPL-3.0-or-later
Conflicts: openxcom
Provides: openxcom, openxcom-git
Submitter: WorMzy
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 8
Popularity: 0.33
First Submitted: 2019-07-01 20:12 (UTC)
Last Updated: 2024-06-10 22:08 (UTC)

Dependencies (20)

Required by (8)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

linuxham commented on 2020-06-20 00:25 (UTC)

I have installed OpenXcom Extended, and gotten it to launch, and tried the X-Files Mod, which failed to run. It complained of missing armor rules. X-Files runs in 6.5.3, but not in your 6.5.4.1.

Ed

gonciarz commented on 2019-07-16 20:49 (UTC) (edited on 2019-07-16 20:52 (UTC) by gonciarz)

Hi WorMzy, I understand that the OpenXcom is dead now because guys do not release on github. But on the other hand I don't like disorder and manual steps. I just want to have all packages (openxcom/git, openxcom-extended/git) Still from my point of view the cleanest solution would be to apply a patch to openxcom that would change the 'data' path to 'UFO'. Actually I dig a bit and prepared one. Please accept it.

I'm not familiar how collaboration looks like on aur git, but I usually create a pull request. I've tested the game and it loads properly. Please take a look here: https://bitbucket.org/gonciarz/openxcom-archlinux/pull-requests/1/path-fix/diff

I believe that after merging that change to aur repo, we may change path in openxcom-data-steam. What do you think?

Regards

WorMzy commented on 2019-07-15 11:35 (UTC)

That's the problem -- openxcom is up to date, everything else pulls a developmental version. ;)

I'm opposed to switching the openxcom-data-steam package to build for -git/-extended packages by default (it's not called openxcom-git-data-steam after all, and it's easy enough to switch), but I don't mind appending to the note in the PKGBUILD to make it clear that a git flagged build is necessary for OXCE too. I'm not sure it will make any difference though -- the package has only attracted one vote and a handful of comments in the 4+ years it's been available, I doubt it's heavily used.

gonciarz commented on 2019-07-15 09:02 (UTC)

Thanks, I may follow your suggestions but if openxcom is not up to date then maybe you may switch defaults in openxcom-data-steam (_openxcom_ver=git) to support more popular version. What do you think?

WorMzy commented on 2019-07-15 08:29 (UTC)

If it depends on OXCE, then it should depend on that package (I'll add a provides=(openxcom-extended) to the -git package, so either of the extended packages will fulfil the requirements).

The openxcom package is packaging v1.0 of openxcom from 5 years ago, this version predates TFTD support which is why it has a different data directory. Until upstream tag a new release, I suggest you package for and depend on openxcom-git (which is the equivalent of the nightly releases recommended by upstream.

gonciarz commented on 2019-07-15 06:50 (UTC)

I just want to cooperate.

SupSuper (OpenXcom) advised that we may put the data to: /usr/share/openxcom/standard

Please take a look at my first mod: https://aur.archlinux.org/packages/openxcom-mod-twots and vote it if you like it :)

My only concern is that this package depends on oxce version of xcom (standalone or git).

I've noticed that there are mods that I need to apply to data/UFO data/TFTD directory, but git and non-git version of OpenXcom keeps either in /usr/share/openxcom/UFO or /usr/share/openxcom/data directory. I believe that we in order to avoid conflicts we should unify those directories and prepare a proper patch for e.g. non-git version. Then openxcom-data-steam package will also work for both versions. What do you think?

WorMzy commented on 2019-07-07 17:15 (UTC)

You don't need to seek approval from me -- if upstream adds "system" mod directory support, then you can add whatever mods you like to the AUR. Just don't make packages that install files to $HOME or you'll incur the wrath of the TUs. ;)

gonciarz commented on 2019-07-07 10:40 (UTC)

WorMzy I was wondering. Maybe we may resurrect UFO/XCOM a bit. mod.io contains some interesting mods. Some of them requires OXCE but we already have a support for it in Arch thanks to you ;). Maybe their corresponding Arch packages could be created. Below I listed the most popular once I have in mind:

463: https://openxcom.mod.io/the-x-com-files 223: https://openxcom.mod.io/40k 49: https://openxcom.mod.io/area-51 115: https://openxcom.mod.io/x-piratez 46: https://openxcom.mod.io/the-world-of-terrifying-silence 163: https://openxcom.mod.io/final-mod-pack

Normally you put mod files to .local/share/openxcom/mods directory. I thought that if we put a mod to /usr/share/openxcom/mods then it will be recognised by the game, however it's not. The game searches for mods in user/mods directory only. From OpenXcom documentation:

user mods, savegames, screenshots config game configuration data UFO and TFTD data files, standard mods, common resources

Thus I opened a feature request to add support for it. Then that should be propagated to OXCE. https://openxcom.org/bugs/openxcom/issues/1455

What do you think about it?

gonciarz commented on 2019-07-07 09:51 (UTC)

Great :)

WorMzy commented on 2019-07-02 09:53 (UTC)

Done. :)

« First ‹ Previous 1 2 3 4 Next › Last »