Add flatpak build

[Totto16]

This provides a flatpak manifest to build aegisub as flatpak application

• it adds a CI that builds it
• it also adds DependencyControl (I find it helpful, to include that in a flatpak build, but ofc it could be changed)
• it fixes some names, that require a certain schema on flatpak (icons, app_name etc.)
• this builds the dependencies like boost, wxWidgets beforehand with their own build system, mainly due to local development concerns, but also to be sure, that no bug occurs in the meson conversion of these dependencies
• it uses
  • lua 5.1
  • wxWidgets 3.2.3
  • boost 1.83.0
  • libass 0.17.1 (this builds from the original repo, but since this manifest is a little bit older, where the meson port didn't have these adjustments, it could be changed to that

[zefr0x]

You might want to look at Aegisub#336.

I'm working on a Flatpak package to be published in Flathub: https://github.com/zefr0x/flathub/tree/aegisub

[Totto16]

You might want to look at Aegisub#336.

I'm working on a Flatpak package to be published in Flathub: https://github.com/zefr0x/flathub/tree/aegisub

Your package seems much more sophisticated, but since the main work for Aegisub/Aegisub is done here, and with meson as build system, with the version of the libraries, that are used here, and this is eventually merged into that repo, it would be better to build on this repo, maybe we could merge the manifests in some way 🤔

[zefr0x]

You might want to look at Aegisub#336.
I'm working on a Flatpak package to be published in Flathub: https://github.com/zefr0x/flathub/tree/aegisub

Your package seems much more sophisticated, but since the main work for Aegisub/Aegisub is done here, and with meson as build system, with the version of the libraries, that are used here, and this is eventually merged into that repo, it would be better to build on this repo, maybe we could merge the manifests in some way 🤔

I don't think that Flathub would accept a fork with no official stable release.

Any way it's easy to use the new build system, noting huge need to be changed (I even have it commented in the manifest).

If Flathub don't have any problems I will relay on TypesettingTools/Aegisub. I will ask them when I open a pull request.

[Totto16]

You might want to look at Aegisub#336.
I'm working on a Flatpak package to be published in Flathub: https://github.com/zefr0x/flathub/tree/aegisub

Your package seems much more sophisticated, but since the main work for Aegisub/Aegisub is done here, and with meson as build system, with the version of the libraries, that are used here, and this is eventually merged into that repo, it would be better to build on this repo, maybe we could merge the manifests in some way 🤔

I don't think that Flathub would accept a fork with no official stable release.

Any way it's easy to use the new build system, noting huge need to be changed (I even have it commented in the manifest).

If Flathub don't have any problems I will relay on TypesettingTools/Aegisub. I will ask them when I open a pull request.

The only main difference between the meson and the autotools version is the flatpak specific things, like .desktop file with name (not aegisub but "org.aegisub.Aegisub") and the icons names, the rest is nearly the same, since I also used the native build systems for the dependencies, but not that many specific options etc. I also added Dependency control, which could be controversial. IMO it's much more concise, to modfiy a few lines of the build system than patching the original code up, to rename these etc. Meson is better integrated than autotools in the flatpak-builder etc.