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
as-utils from appstream-glib need to be included in appstream #299
Comments
|
I will not blindly add all of as-utils, especially if nothing uses functions from it within AppStream, and also because there are a lot of duplicates. |
That's a problem, though, since the icons and such are in a tarball. |
|
Well, you could just extract that stuff in dnf. But libappstream also has a vendor-specific function on Debian functions that just calls tar to unpack stuff, maybe that's good enough as well. |
|
I added this feature as API function now. I do think that the metadata should be installed and extracted by the package manager explicitly though, rather than using a function that relies on heuristics to determine some of its values. By the way, @hughsie : Do you really want the appstream-glib variant of this feature creating world-readable directories? ;--) |
There's almost no point in DNF doing it, since it can't really use the data for anything. That's why PackageKit does it instead. |
There are a number of utility functions in appstream-glib that do not exist in appstream, and without them, it'd basically impossible to migrate to libappstream.
For example, I cannot migrate PackageKit's libappstream-glib dependency to libappstream because
as_utils_install_filename()is used in the DNF backend:https://github.com/hughsie/PackageKit/blob/ed73aa6317595d2c2f1bda7990cbd64efb133f84/backends/dnf/pk-backend-dnf.c#L524-L545
The text was updated successfully, but these errors were encountered: