- 13 Aug, 2019 3 commits
-
-
Matthias Klumpp authored
This adds a few checks and cleanups for the release metadata, most importantly validating the release dates for correctness. See issue #245 for more information.
-
Matthias Klumpp authored
This resolves #245
-
Matthias Klumpp authored
-
- 12 Aug, 2019 7 commits
-
-
Matthias Klumpp authored
-
Matthias Klumpp authored
-
Matthias Klumpp authored
-
Matthias Klumpp authored
This was already made clear in the spec part of the documentation, but the quickstart page was not up to date.
-
Matthias Klumpp authored
The answer is: Pretty much use .metainfo.xml all the time, unless you have a desktop-app in which case you may choose .appdata.xml (which will likely be supported forever for legacy compatibility).
-
Matthias Klumpp authored
We don't use deprecated API anymore and are slightly faster. In theory we can get rid of a few more allocations here, but let's see if that is actually needed for better performance.
-
Matthias Klumpp authored
-
- 10 Aug, 2019 1 commit
-
-
Adolfo Jayme Barrientos authored
Currently translated at 100.0% (197 of 197 strings)
-
- 08 Aug, 2019 4 commits
-
-
Igor authored
Currently translated at 100.0% (197 of 197 strings)
-
Matthias Klumpp authored
-
Matthias Klumpp authored
-
Matthias Klumpp authored
This is nice for automated tools that need to read this data for further processing.
-
- 06 Aug, 2019 3 commits
-
-
Matthias Klumpp authored
Previously, AppStream would read and releases from metainfo files, then ensure that they were sorted and make a sorted list of releases available to the user. Now, we only sort before data is serialized, not when it is loaded. Additionally, the validator will emit a warning (failing validation) when releases in a metainfo files are not sorted correctly.
-
Matthias Klumpp authored
A latest-to-oldest release info is now be strongly advised ("should") for metainfo files, while being mandatory for collection metadata ("must"). We might enforce this ordering for all metainfo files soon, if there are no issues found with this change.
-
Matthias Klumpp authored
-
- 05 Aug, 2019 1 commit
-
-
Matúš Baňas authored
Currently translated at 100.0% (197 of 197 strings)
-
- 03 Aug, 2019 1 commit
-
-
Matthias Klumpp authored
By default, `appstreamcli validate*` commands will now display a terse list of found issues. You can pass `--explain` to the command in order to get a detailed explanation on the individual issues.
-
- 02 Aug, 2019 8 commits
-
-
Anders Jonsson authored
Currently translated at 100.0% (197 of 197 strings)
-
Heimen Stoffels authored
Currently translated at 100.0% (197 of 197 strings)
-
Milo Casagrande authored
Currently translated at 100.0% (197 of 197 strings)
-
Balázs Úr authored
Currently translated at 100.0% (197 of 197 strings)
-
Ryo Nakano authored
Currently translated at 79.7% (157 of 197 strings)
-
yurchor authored
Currently translated at 100.0% (197 of 197 strings)
-
Rafael Fontenelle authored
Currently translated at 100.0% (197 of 197 strings)
-
Matthias Klumpp authored
This is rudimentary for now and will look much better soon. But it allows to test the new validator more easily in the master branch.
-
- 01 Aug, 2019 4 commits
-
-
Matthias Klumpp authored
With this new validation system each issue gets a long explanation as well as a unique short tag which can be used for display it better in UIs, ignore it or just quickly infer what the problem is. This is a semi-breaking change as it will change the validator output, so this will receive further updates in the next few days to make it work better and display the output better.
-
Piotr Drąg authored
Currently translated at 100.0% (197 of 197 strings)
-
Ryo Nakano authored
Currently translated at 79.2% (156 of 197 strings)
-
Mesut Akcan authored
Currently translated at 100.0% (197 of 197 strings)
-
- 31 Jul, 2019 2 commits
-
-
Matthias Klumpp authored
This is just to make naming consistent everywhere, in the code as well as in printed messages. For validation, severity == importance
-
Matthias Klumpp authored
-
- 30 Jul, 2019 2 commits
-
-
Matthias Klumpp authored
This particular case of a component being an addon to itself is nonsense, but people may make that mistake and we shouldn't crash in that case. With this patch the cache will be resilient against such cases and simply ignore components depending on themselves. We could still get nasty dependency loops though, with A depending on B depending on A. This is a bit more complicated to resolve and will be fixed in a future commit. Resolves: #243
-
Matthias Klumpp authored
This should not fail, ever, unless we run out of memory. But since I was looking at that code, having a sanity check here is better in case this does become more relevant in future (and simply because not checking it was not good prectice).
-
- 22 Jul, 2019 1 commit
-
-
Bojan authored
Currently translated at 12.7% (25 of 197 strings)
-
- 13 Jul, 2019 3 commits
-
-
Matthias Klumpp authored
-
Matthias Klumpp authored
Ensure we never accidentally free unallocated memory.
-
Matthias Klumpp authored
-