Spec URL: http://ignatenkobrain.fedorapeople.org/for-review/createrepo_as.spec SRPM URL: http://ignatenkobrain.fedorapeople.org/for-review/createrepo_as-0.1.0-1.git801136f.fc21.src.rpm Description: createrepo_as is a tool that allows us to create AppStream metadata from a directory of packages. It is typically used when generating distribution metadata, usually at the same time as modifyrepo or createrepo. What this tool does: * Searches a directory of packages and reads just the RPM header of each. * If a package contains an interesting file, just the relevant files are decompressed from the package archive. * A set of plugins are run on the extracted files, and if these match certain criteria CraApplication objects are created. * Any screenshots referenced are downloaded to a local cache. This is optional and can be disabled with --nonet. * When all the packages are processed, some of the CraApplication objects are merged into single applications. This is how fonts are collected. * The CraApplication objects are serialized to XML and written to a compressed archive. * Any application icons or screenshots referenced are written to a .tar archive. Fedora Account System Username: ignatenkobrain
New SPEC: http://ignatenkobrain.fedorapeople.org/for-review/createrepo_as.spec New SRPM: http://ignatenkobrain.fedorapeople.org/for-review/createrepo_as-0.1.0-2.gita71cb63.fc21.src.rpm
New SRPM: http://ignatenkobrain.fedorapeople.org/for-review/createrepo_as-0.1.0-3.git54aaec2.fc21.src.rpm
not that we can't have a standalone package to make AppStream metadata, for use in Fedora's tooling it must be integrated into createrepo
(In reply to Dennis Gilmore from comment #3) > not that we can't have a standalone package to make AppStream metadata, for > use in Fedora's tooling it must be integrated into createrepo because now it's under actively developing I think we can add this package now and when it will be stable merge into createrepo (but I'm not sure. Richard is a developer. not mine).
(In reply to Dennis Gilmore from comment #3) > not that we can't have a standalone package to make AppStream metadata, for > use in Fedora's tooling it must be integrated into createrepo Igor is right; we're still making additions to the spec and finding edge cases we have to handle. At the moment the complexity and requirement that we call the same code from createrepo and createrepo_c I'm thinking to either make this a GIR introspectable library we can call from python and C, or just a single binary we can call from either tool. We're a few months off doing this tho (although we're getting closer to AppStream 1.0 every day) and having a seporate package would make it much easier for the people running other repos for Fedora and RHEL. Thanks, Richard
This morning I've merged the small tool we need for generation into the appstream-glib package. This makes it easier to track AppStream API changes rather than in two projects and for two release schedules.