```
$ appstreamcli compose waydroid-install-prefix/
Automatically selected 'install/' as data output location.
WARNING: Metadata origin not set, using 'example'
Processing directory: install/
Composing metadata...
Run failed, some data was ignored.
Errors were raised during this compose run:
id.waydro.waydroid
E: no-valid-category
Refer to the generated issue report data for details on the individual problems.
```
https://specifications.freedesktop.org/menu-spec/latest/category-registry.html
This fixes composing waydroid into a catalog when using appstream.
Without it waydroid will fail to be included in the catalog for distros
that use `appstream-generator`.
Add XDG directory and menu files
to have a Waydroid menu directory with all Waydroid apps,
and avoid having them in a 'Lost & Found' menu directory
---------
Co-authored-by: Taha <62564400+inspectorgadget03@users.noreply.github.com>
* Some tools break when the first line is not the xml header
* Some tools require the icon to not be a symlink. There should be no
more users of ./data/AppIcon.png so just move it to its location
* Update contact information.
(How did that translation URL end up in there?)
* Remove too large screenshot
After 85843da (container: Make "waydroid-net.sh start" failure fatal)
this could result always failing to start unless you ran
"waydroid-net.sh stop" manually first; perhaps this should always be
stopped upon encountering errors?
We were implicitly using proc:mixed to mount /proc/sys as read-only.
Without the automount the whole /proc was mounted as read-write which
we want to avoid.
I'm unable to replicate the proc:mixed logic with lxc.mount.entry
so revert this change until a solution is found.
This reverts commit f5543df686.
Fixes: #642
The "default to waydroid0" was broken as awk never returned a non-zero
exit code if the file exists but no match was found. Also account for
the key being named lxc.network.link on older LXC versions so one still
has the ability to have a flexible Waydroid network configuration.
What used to be called 'config_2' was actually meant to be used with
LXC 3.0 and later, so call it config_3 and fix the logic.
Also lxc.pty.max is an LXC 3.0 feature
Split config files into snippets isolating new LXC features by version.
Move `seccomp.allow_nesting` to version 4 or higher.
NOTE: this currently assumes that new LXC versions will keep compatibility
with old config options. The only exception to this was LXC 1.x -> 2.x
