GNOME Bugzilla – Bug 707226
wget of appstream icons requires networking
Last modified: 2013-09-06 12:19:57 UTC
...which gnome-ostree denies for GPL compliance reasons. The main option that comes to mind now is to just check them into git. If they don't change too often, this isn't bad. Particularly if we do it as an exploded tree and not a tarball. It does seem to me though this data will likely need to be updated dynamically (i.e. from a web service) in the longer term.
For now: https://git.gnome.org/browse/gnome-ostree/commit/?id=dc946185c20d61da163e09e131953676ffd805bf
This might also be problematic for downstreams (ex. fedora) for the same reasons.
Lets not discuss fedora here; there's a long and painful history there wrt shipping any useful metadata. This xml file is a shortterm workaround for the lack of such information in repositories. We can certainly check it in.It
Note that the appstream data is disted, so fedora will be fine; the data ends up in the tarball. ostree is more stringent in requiring that building from git works without network.
(In reply to comment #4) > Note that the appstream data is disted, so fedora will be fine; the data ends > up in the tarball. OK. > ostree is more stringent in requiring that building from git > works without network. Even if it allowed network "wget -N" does not work with the busybox wget (which ostree use).
I've switched ostree to use --enable-offline-appstream-data=no
So presently for gnome-ostree, what I could probably do is just compose appdata for the applications that are in the tree itself. But the obvious thing to do is to have a separate application format and a web service and such on gnome.org too.