Arch Linux User Repository

For users compiling this on Raspberry Pi with Arch Linux ARM, go to common.h and uncomment this on line 27:

// #define RASPBIAN // Raspberry Pi requires a few tweaks. Define RASPBIAN to activate them or comment this line out.

Thanks for updating this to the latest version 9.55.

Since early 2023 LAC has undergone a flurry of new versions because some of the most popular desktop LINUX distros got updates that somehow rendered LAC's built-in menus useless (All menu buttons are displayed properly, but nothing happens when they are clicked).

This has been fixed with a new, companion program named "LacMenuLauncher" that provides a new and independent set of menus for LAC. If LAC's built-in menus work for you, then you don't need the LacMenuLauncher. Otherwise you will want it. Learn all about it here:

https://sourceforge.net/p/linuxaircombat/discussion/lacmenulauncher/

With this version 9.55 LAC has been adapted for either set of menus and seems to be stable. I think the flurry of new LAC versions is over. THANKS for this update.

Also, thanks for bumping the version and addressing the two notes below so far!

@alfrednewman: the problem with both $variable and ${variable} in a shell is how it is expanded, e.g. how the value is being "inserted" here. If the directory you're building the project in is my builds (with a space), then a statement such as rm ${pkgdir} will actually be expanded and executed as rm "my" "builds", or effectively

rm my
rm builds

This of course applies to any command. And the issue is not just with space but with some other symbols in directory names. It's quite unfortunate that shells do it this way -- and even have to do it this way to be POSIX conformant -- but that's the state of things.

PKGBUILDs are essentially somewhat structured shell scripts, and its syntax and rules for variable expansion apply as well.

@vasya I have just updated LAC to the latest version available. I've deleted the two unused variables that you brought up. I don't think it is necessary for $pkgdir to be used in quotes, but the curly brackets work fine. What do you mean by "regardless of which directory its cloned to"? $pkgdir is already relative to the folder its cloned to.

Hi! To maintainers: could you please fix some of the PKGBUILD issues? I'm trying to install the game via rua (warning: it's my own tool), and it gives a bunch of warnings, some perfectly legit I think.

_filename='Lac${pkgver}' seems to be unused. It is also quoted improperly (single quotes instead of double quotes), but even if the quotes would be correct, there's just no reason to keep the variable.

The variable RESOURCE_DIR (in capitals) is never used. The only used variable is the one in lowercase and with an underscore.

All instances of $pkgdir should ideally have double quotes around them, so that a build would work regardless of which directory the AUR project is cloned to.

I'm happy to make/propose all those changes myself as well, if desired.

Thanks regardless for the packaging of the game!

Appimage version here: https://aur.archlinux.org/packages/linux-air-combat-appimage

15Jun2023: I confirm that this package works perfectly on the current version of Manjaro Linux. Further details here:https://sourceforge.net/p/linuxaircombat/discussion/manjarolinuxandlac/thread/b0eb8b724f/

Thanks for updating this to version 8.83. Users wishing to learn of the resulting changes can always consult the online ChangeLog at:

https://askmisterwizard.com/2019/LinuxAirCombat/LinuxAirCombatChangeLog.htm