Great news for the LAC community: Several expert repository "Packagers" have expressed positive opinions of LAC and have placed our little flight simulator into "the queue" for the packaging work that is necessary for its availability in their Repositories! Here are a couple of links to some of the related discussions:
In support of those efforts, I am developing a special version of LAC that they may use as the basis for their work. If this option is selected, no new features will be directly visible to users, but LAC's components are installed in a different manner and end up in different filesystem locations: LACs executable ends up in the /usr/bin filesystem alongside most other applications. LAC's other required resource files end up in the /usr/share filesystem according to long-established LINUX norms. User-specific configuration files like our "LacConfig.txt" file remain in the user's ~home/.LAC folder as at present.
I don't know for sure whether these experts will base their packaging work on this new version of LAC, but I will offer it as an option. When I'm ready to release it, I will provide a link from this "LAC in LINUX Repositories" forum.
Last edit: bbosen 2020-10-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In support of the work being done by various LINUX distro/repository packagers, I finished LAC Version 8.35 (Lac08p35) on 10Oct2020. Users that configure LAC according to prevailing norms see no new features or bug fixes, but filesystem locations and installation processes are more in line with LINUX conventions, so I hope this version will assist in the software packaging process. That version 8.35 was originally published in our SourceForge archives according to the well-established pattern, but it has subsequently been superceded with later versions.
As you would expect, for all of these versions, after extracting the archive and entering into the resulting source code folder from a bash shell, the commands to compile, link, install, configure, and run it are:
make
make clean
make install
run ./install as root and then exit from root authority
lac (first execution completes essential configuration steps)
lac (all subsequent executions run according to our well-known, published documentation)
I have tested this with success on several LINUX distros (most recently on Raspbian).
Last edit: bbosen 2021-05-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Update: in November 2020 I found and fixed two tiny bugs in "Peabody's Mission", one of the seven "TEST" missions that are available for further testing and improvement by mission developers. As a consequence, a newer installation archive benefitting from these two bug fixes and configured for global installation in the "/usr" filesystem was published in our SourceForge archives, according to the usual pattern, on 19Nov2020.
I recommended use of that new Lac08p37.tar.gz archive by LINUX Repository packagers. It follows the pattern described above: The executable is named "lac" and is installed at /usr/bin/lac. The shared data files are stored in a new folder at /usr/share/LAC, and user-specific configuration files are built at run-time as needed in a new, hidden folder named ".LAC" within the user's home folder.
I have tested this with success on several LINUX distros (most recently on Debian LINUX).
Last edit: bbosen 2021-05-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I started a brand-new thread about LAC in the Debian forums, hoping to inspire help from one of their highly skilled, very busy Repository Packagers. Here's a link to the new thread:
Steve Pusser has completed all of the "heavy lifting" for us, and has published LAC in a "Repository-style" package for several LINUX distros including Debian9, Debian10, and Raspbian, for X86 and ARM architectures! Here's the primary link to his work:
As a consequence of Steve's work, it should be easier hereafter for many other LINUX distros to publish easy access to LAC in repositories (both "official" and "unofficial"). This is just one step toward ubiquitous availability for LAC, but it's a very significant step.
Last edit: bbosen 2021-05-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Great news for the LAC community: Several expert repository "Packagers" have expressed positive opinions of LAC and have placed our little flight simulator into "the queue" for the packaging work that is necessary for its availability in their Repositories! Here are a couple of links to some of the related discussions:
Debian Linux: http://forums.debian.net/viewtopic.php?f=16&t=145168&sid=809f2267560c824ebd63a19a663fd827
MX Linux: https://forum.mxlinux.org/viewtopic.php?f=55&t=56792
In support of those efforts, I am developing a special version of LAC that they may use as the basis for their work. If this option is selected, no new features will be directly visible to users, but LAC's components are installed in a different manner and end up in different filesystem locations: LACs executable ends up in the /usr/bin filesystem alongside most other applications. LAC's other required resource files end up in the /usr/share filesystem according to long-established LINUX norms. User-specific configuration files like our "LacConfig.txt" file remain in the user's ~home/.LAC folder as at present.
I don't know for sure whether these experts will base their packaging work on this new version of LAC, but I will offer it as an option. When I'm ready to release it, I will provide a link from this "LAC in LINUX Repositories" forum.
Last edit: bbosen 2020-10-09
In support of the work being done by various LINUX distro/repository packagers, I finished LAC Version 8.35 (Lac08p35) on 10Oct2020. Users that configure LAC according to prevailing norms see no new features or bug fixes, but filesystem locations and installation processes are more in line with LINUX conventions, so I hope this version will assist in the software packaging process. That version 8.35 was originally published in our SourceForge archives according to the well-established pattern, but it has subsequently been superceded with later versions.
As you would expect, for all of these versions, after extracting the archive and entering into the resulting source code folder from a bash shell, the commands to compile, link, install, configure, and run it are:
make
make clean
make install
run ./install as root and then exit from root authority
lac (first execution completes essential configuration steps)
lac (all subsequent executions run according to our well-known, published documentation)
I have tested this with success on several LINUX distros (most recently on Raspbian).
Last edit: bbosen 2021-05-09
Update: in November 2020 I found and fixed two tiny bugs in "Peabody's Mission", one of the seven "TEST" missions that are available for further testing and improvement by mission developers. As a consequence, a newer installation archive benefitting from these two bug fixes and configured for global installation in the "/usr" filesystem was published in our SourceForge archives, according to the usual pattern, on 19Nov2020.
I recommended use of that new Lac08p37.tar.gz archive by LINUX Repository packagers. It follows the pattern described above: The executable is named "lac" and is installed at /usr/bin/lac. The shared data files are stored in a new folder at /usr/share/LAC, and user-specific configuration files are built at run-time as needed in a new, hidden folder named ".LAC" within the user's home folder.
I have tested this with success on several LINUX distros (most recently on Debian LINUX).
Last edit: bbosen 2021-05-09
I started a brand-new thread about LAC in the Debian forums, hoping to inspire help from one of their highly skilled, very busy Repository Packagers. Here's a link to the new thread:
http://forums.debian.net/viewtopic.php?f=8&t=149274
More good news:
Steve Pusser has completed all of the "heavy lifting" for us, and has published LAC in a "Repository-style" package for several LINUX distros including Debian9, Debian10, and Raspbian, for X86 and ARM architectures! Here's the primary link to his work:
https://build.opensuse.org/package/show/home:stevenpusser:LAC/linux-air-combat
As a consequence of Steve's work, it should be easier hereafter for many other LINUX distros to publish easy access to LAC in repositories (both "official" and "unofficial"). This is just one step toward ubiquitous availability for LAC, but it's a very significant step.
Last edit: bbosen 2021-05-09
Steve Pusser has continued his work to make LAC easily available in additional LINUX Repositories. It looks like he has succeeded with MX LINUX too!
https://forum.mxlinux.org/viewtopic.php?f=57&t=39874&p=638895&hilit=linux+air+combat#p638895