FS#48104 - [archlinux-appstream-data] shouldn't depend on appstream
Attached to Project:
Community Packages
Opened by Aleix Pol (apol) - Tuesday, 09 February 2016, 00:14 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 09 February 2016, 20:04 GMT
Opened by Aleix Pol (apol) - Tuesday, 09 February 2016, 00:14 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 09 February 2016, 20:04 GMT
|
Details
Description:
It would be good if the dependency was in fact the other way around, and the libraries depended on the metadata, or even the applications depended on the metadata (i.e. gnome-software and discover). This would be best as there's different implementations that will read the metadata and, therefore it's not mandatory to have appstream if the applications are going to read the metadata themselves (or appstream-glib for that matter). |
This task depends upon
Closed by Antonio Rojas (arojas)
Tuesday, 09 February 2016, 20:04 GMT
Reason for closing: Deferred
Additional comments about closing: will replace with hooks in the near future
Tuesday, 09 February 2016, 20:04 GMT
Reason for closing: Deferred
Additional comments about closing: will replace with hooks in the near future
Comment by Antonio Rojas (arojas) -
Tuesday, 09 February 2016, 07:09 GMT
Comment by Antonio Rojas (arojas) -
Tuesday, 09 February 2016, 20:04 GMT
The dependency is needed to update the database in the
post-install script
Once hooks are fully operational we can replace the
post-install/post-update scripts with hooks in the appstream and
appstream-glib packages that run their respective db refresh
commands when the appstream data is updated. But it looks like
there are still some issues to iron out with hooks, so we need to
keep the dependency for now.