| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
The AppImage validation tools complain even when one follows their
recommendations on supplying AppStream metadata and with correctly named
files. I'm now starting to understand why most AppImages don't bother
with it.
|
| |
|
|
|
| |
Also installs some tools for appstream validation, which unfortunately
show that currently the appstream file used has some issues.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
in appimage as well, just in case
|
| | |
|
| | |
|
| |
|
|
| |
steps manually; first attempt to build tarball on ubuntu 16.04
|
| |
|
|
|
|
|
|
|
|
| |
Switching to an Arch based build process for easier maintenance and
using specific runners for tasks where that might be necessary.
Right now, parent/child pipelines for somewhat parallel builds for
different architectures / semi-independent pak-builds don't seem to
properly work yet due to `trigger:` not being recognized when it should,
so that's not yet implemented.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
