| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Commit 5cbcfe05ec missed updating appstream-util's bash completion
for the new command, do that now.
|
|
|
|
| |
2020 seemed like such a long time in the future all those years ago...
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Require <content_rating> for any desktop or console application
* Make <release> mandatory when validating
* Further relax style requirements
* Require description for desktop an console apps
This changes a lot of things that are now best practice for all apps, and
required to be included in Flathub.
Use `appstream-util validate-relax` to ignore some new failures and use
`appstream-util validate-strict` to bring them back.
Fixes: https://github.com/hughsie/appstream-glib/issues/263
|
| |
|
|
|
|
| |
Firmware should now be distributed using the LVFS and consumed by fwupd.
|
| |
|
|
|
|
|
|
|
| |
This allows us to support desktop-less components that specify a cached icon.
The icon search code has been split into a new plugin that is run after the
appdata and desktop plugins have added the AsbApp to the list of available apps.
|
|
|
|
|
| |
This enables a lot of software to comply with the GDPR and also allows us to
show translated warning and EULA text to unsuspecting users.
|
| |
|
|
|
|
| |
follow-up from commit 9df56f2
|
| |
|
|
|
|
|
|
|
|
| |
This makes asglib align with the AppStream spec, which sees
/usr/share/metainfo as the canonical location for storing metadata, and
/usr/share/appdata as legacy (but still must-be-supported) location.
Signed-off-by: Richard Hughes <richard@hughsie.com>
|
|
|
|
|
|
| |
Accidentally dropped when ported to meson
Fixes: https://github.com/hughsie/appstream-glib/issues/183
|
| |
|
|
|
|
|
|
|
| |
Depend on the value of the `enable-man` option, as well as the presence
of xsltproc. This is necessary, as not all builders allow connecting to
the network to download the XSLT style sheet for turning docbook into
man pages, for instance.
|
| |
|
|
|
|
| |
This can be relaxed using the validate-relax command.
|
| |
|
|
|
|
| |
Fixes: https://github.com/hughsie/appstream-glib/issues/153
|
|
|
|
|
|
|
| |
The most recent release has to be listed first in the file.
Check the version number and release timestamp to verify this.
Fixes: https://github.com/hughsie/appstream-glib/issues/153
|
| |
|
|
|
|
|
| |
Translators sometimes leave extra whitespace, so if we're parsing without
AS_NODE_FROM_XML_FLAG_LITERAL_TEXT then just swallow the trailing spaces.
|
|
|
| |
DISTCHECK_CONFIGURE_FLAGS is only for users to override AM_DISTCHECK_CONFIGURE_FLAGS. It's not possible to do if Automake files stomp on that.
|
|
|
|
|
|
|
|
|
|
|
| |
I don't want to maintain this large chunk of complex code in the main library,
especially as it's basically unused except for the validation of .cab files.
The latter has a python implmentation as used on the LVFS, so it's really just
dead code now.
Move the (unused) implementation to libginf for archival, but leave stubs in to
avoid upsetting the API/ABI checkers. We can remove the symbols when we next
break soname.
|
|
|
|
| |
Also include the branch in the unique-id for equality.
|
|
|
|
|
|
| |
/usr/share/appdata is the old location, but will be supported for a long time.
Replaces https://github.com/hughsie/appstream-glib/pull/112
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The idea is to encode the scope and user-specified origin in the filename as
flatpak remotes have metadata with the filename `appstream.xml.gz` that have
origin harcoded to 'flatpak'.
We can't set a custom origin when generating the metadata as the remote name
is set client side and can be any string the user chooses.
It's also expected that something like gnome-software will keep the symlink
cache up to date. I'm using ~/.local/share/app-info/xmls at the moment, but if
we decide that the data is actually gnome-software specific then it can move.
|
|
|
|
|
| |
This makes the parser read new-style cached icons, local and remote
icons when they are present in DEP-11 YAML.
|
|
|
|
|
|
|
|
| |
This doesn't actually tell you what tag is invalid, which is a tradeoff between
producing someting and also not slowing parsing down for very broken AppStream
metadata files.
Fixes: https://github.com/hughsie/appstream-glib/issues/94
|
|
|
|
| |
Fixes https://github.com/hughsie/appstream-glib/pull/92
|
|
|
|
| |
This is not maintained *at all* and Ubuntu is soon to be shipping AppStream.
|
|
|
|
| |
Fixes: https://github.com/hughsie/appdata-tools/issues/26
|
|
|
|
| |
Fixes https://github.com/hughsie/appstream-glib/issues/81
|
|
|
|
|
| |
This allows upstream to specify the translation domain so we can calculate the
language statistics automatically without using hacky heuristics.
|
| |
|
|
|
|
|
|
|
| |
This is a simple app that takes a prefix (default /usr) and a set of
app names. It looks for appdata, desktop and icon files with that
basename in $prefix/share/[appdata|applications|icons] and generates
appstream xml files + icons in (by default) $prefix/share/app-info.
|
|
|
|
| |
Also, use the new functionality in the existing gettext builder plugin.
|
| |
|
|
|
|
|
|
|
| |
Recent gettext release has a feature to allow consumer projects to
supply their own string extraction rules for XML files, in ITS format.
Gettext itself ships the rules for AppData, but it would be better
maintained in the upstream project.
|
|
|
|
| |
Fixes https://github.com/hughsie/appstream-glib/issues/73
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If we're comparing versions that are both converted to strings it doesn't
really matter how the strings are stored (e.g. AA.BB.CC.DD or AA.BB.CCDD) as
the integer rules still apply **if** we don't remove the prefixed zeros.
The only time we have to be careful is where the firmware metainfo uses the
triplet and the .inf file uses the hex version format.
By using the triplet-style by default we match what Intel and Microsoft are
providing in the firmware release notes.
Basically:
* If you're not using the MS-style versioning scheme, just use hex numbers in
both places.
* If you don't care about applying the update on Microsoft Windows, just
don't supply an .inf file at all.
Fixes the other half of https://github.com/hughsie/fwupd/issues/34
This does break API, but we've never had the method in a released version so
I think it's fine to break at this stage. Make sure you update fwupd at the same
time if you're using git master.
The last bit of this fix would to be somehow encode the "display version" onto
the AppStream <release> object, but this needs discussion upstream first.
|
|
|
|
| |
Fixes half of https://github.com/hughsie/fwupd/issues/34
|
|
|
|
| |
There's no point having two implementations of the same thing.
|
| |
|
| |
|
|
|
|
|
|
| |
This allows us to have an ID that isn't tied to the GUID, and also allows us to
have one component that targets more than one ESRT GUID. This requires changing
the matching logic better, but should match what makes it into AppStream 0.9
|
|
|
|
|
|
| |
This allows the release engineer to _only_ update the metainfo.xml file for
each release. If the firmware.inf file is not being used in Windows for driver
installation then we should make the file static.
|
|
|
|
| |
It makes the story unclear when there are two ways of specifying the location.
|