mirror of
https://github.com/dcs-liberation/dcs_liberation.git
synced 2025-11-10 14:22:26 +00:00
cc3e3a8fa1
Bumps [pyinstaller](https://github.com/pyinstaller/pyinstaller) from 5.13.1 to 6.0.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pyinstaller/pyinstaller/releases">pyinstaller's releases</a>.</em></p> <blockquote> <h2>v6.0.0</h2> <p>Please see the <a href="https://pyinstaller.org/en/v6.0.0/CHANGES.html#id1">v6.0.0 section of the changelog</a> for a list of the changes since v5.13.2.</p> <h2>v5.13.2</h2> <p>Please see the <a href="https://pyinstaller.org/en/v5.13.2/CHANGES.html#id1">v5.13.2 section of the changelog</a> for a list of the changes since v5.13.1.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pyinstaller/pyinstaller/blob/develop/doc/CHANGES.rst">pyinstaller's changelog</a>.</em></p> <blockquote> <h2>6.0.0 (2023-09-22)</h2> <p>Features</p> <pre><code> * (macOS) PyInstaller now attempts to preserve the ``.framework`` bundles when collecting shared libraries from them. If a shared library is to be collected from a ``.framework`` bundle, the ``Info.plist`` is also automatically collected. The ``.framework`` bundle collection code also attempts to fix the bundles' structure to conform to code-signing requirements (i.e., creation of the ``Current`` symbolic link in the ``Versions`` directory, and top-level contents being symbolic links that point to counterparts in the ``Versions/Current`` directory). Note that other resources (for example from ``Resources`` or ``Helpers`` directories) still need to be explicitly collected by hooks. (:issue:`7619`) * (macOS) The file relocation mechanism in ``BUNDLE`` that generates macOS .app bundles has been completely redesigned. All data files are now placed into directory structure rooted in ``Contents/Resources``, all shared libraries (as well as nested .framework bundles) are placed into directory structure rooted in ``Contents/Frameworks``, and only the the program executable is placed into the ``Contents/MacOS`` directory. The contents of ``Contents/Resources`` and ``Contents/Frameworks`` directories are cross-linked via symlinks between the two directory trees in order to maintain illusion of mixed-content directories (in both directory trees). The cross-linking is done at either file level or (sub)directory level, depending on the content type of a (sub)directory. For directories in ``Contents/Frameworks`` that contain a dot in the name, a work-around is automatically applied: the directory is created with a modified name that does not include the dot, and next to it, a symbolic link is created under the original name and pointing to the directory with modified name. (:issue:`7619`) * (non-Windows) PyInstaller now attempts to preserve the parent directory structure for shared libraries discovered and collected by the binary dependency analysis, instead of automatically collecting them into the top-level application directory. Due to library search path assumptions made in various places, symbolic links to collected libraries are created in the top-level application directory. This complements earlier work (:issue:`7028`) that implemented DLL parent directory structure preservation on Windows. (:issue:`7619`) * (Windows) Add an option to hide or minimize the console window in console-enabled applications, but only if the program's process owns the console window (i.e., the program was not launched from an existing console window). (:issue:`7729`) * (Windows) The :option:`--add-data` and :option:`--add-binary` options accept the POSIX syntax of ``--add-data=source:dest`` rather than ``--add-data=source;dest``. The latter will continue to work on Windows to avoid breaking backwards compatibility but is discouraged in favour of the now cross platform format. (:issue:`6724`) * Add automatic binary vs. data file (re)classification step to the analysis process. PyInstaller now inspects all files passed to ``Analysis`` via </tr></table> </code></pre> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="7001defa6f"><code>7001def</code></a> Release v6.0.0. [skip ci]</li> <li><a href="87cda61c09"><code>87cda61</code></a> building: fix executable-bit preservation for collected shell scripts</li> <li><a href="d1adaed16d"><code>d1adaed</code></a> tests: add a test with bundled shell script</li> <li><a href="8bbc4f72bc"><code>8bbc4f7</code></a> bootloader: onefile: set executable bit only on extracted binaries</li> <li><a href="3bd5160ee7"><code>3bd5160</code></a> building: use <code>shutil.copyfile</code> when copying files into onedir build</li> <li><a href="3b4099bdb1"><code>3b4099b</code></a> Cherry pick v5 release commits into develop. [skip ci]</li> <li><a href="962ac8ff4c"><code>962ac8f</code></a> hookutils: remove requirements_for_package</li> <li><a href="984545a775"><code>984545a</code></a> hookutils: adjust behavior of collect_data_files with include_py_files</li> <li><a href="deb6613da8"><code>deb6613</code></a> hookutils: have collect_all look up the dist from package name</li> <li><a href="e4e6ea345b"><code>e4e6ea3</code></a> hookutils: implement replacement for is_module_satisfies</li> <li>Additional commits viewable in <a href="https://github.com/pyinstaller/pyinstaller/compare/v5.13.1...v6.0.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/dcs-liberation/dcs_liberation/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
(Github Readme Banner and Splash screen Artwork by Andriy Dankovych, CC BY-SA 4.0)
About DCS Liberation
DCS Liberation is a DCS World turn based single-player or co-op dynamic campaign. It is an external program that generates full and complex DCS missions and manage a persistent combat environment.
Downloads
Latest release is available here : https://github.com/dcs-liberation/dcs_liberation/releases
To download preview builds of the next version of DCS Liberation, see https://github.com/dcs-liberation/dcs_liberation/wiki/Preview-builds.
DCS bugs
These DCS bugs prevent us from improving AI behavior. Please upvote them! (But please don't spam them with comments):
Bugs and feature requests
If you need to report a bug or want to suggest a new feature, you can do this on our bug tracker. In either case, please use the search bar at the top of the page to see if it has already been reported. Note that you may need to remove the filter for open bugs if it's something we've recently fixed.
Roadmap
Our plans for future releases can be found on our Projects page. Each planned release has a Project, and the page for that project has columns for to do, in progress, and done. Items in the Done column are in the preview build for that release. Items in the To do column are planned to be added to that release.
Resources
Tutorials, contributors and developer's guides are available in the project's Wiki
Special Thanks
First, a big thanks to shdwp, for starting the original DCS Liberation project.
Then, DCS Liberation uses pydcs for mission generation, and nothing would be possible without this. It also uses the popular Mist lua framework for mission scripting.
Excellent lua scripts DCS Liberation uses as plugins:
- For the JTAC feature, DCS Liberation embeds Ciribob's JTAC Autolase script.
- Walder's Skynet-IADS is used for Integrated Air Defense System.
Please also show some support to these projects !