New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unclear documentation #104
Comments
The configuration file is supposed to be crafted manually by the user according to their needs (see https://github.com/ximion/appstream-generator/blob/master/docs/asgen-config.md ). You could of course have it generated from an external tool as well (and I do know people who do that), it's really up to you :-) These files can probably quite easily be autogenerated from a master template for things like Copr.
Run
Yes - ideally you keep the whole workspace directory intact, but at the very least for incremental data generation the |
Can you point me to tools that are able to generate this file? |
Oh, I don't have those, this stuff is used internally in systems for some vendors. But I assume it's basically a "fetch all values from a database or other sensible location, and then feed that info into a dict that gets serialized by Python's json module" kind of deal. |
Spinning off the discussion from rpm-software-management/createrepo_c#75 (comment)
I am investigating whether we can use
appstream-generatorfor Copr instead of appstream-builder. But even after reading all the documentation and man pages and output of--helpI still do not know how to useappstream-generator.My questions are:
The text was updated successfully, but these errors were encountered: