Skip to content
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

API assumes there's one of each appstream id #57

Closed
aleixpol opened this issue Jul 27, 2016 · 2 comments
Closed

API assumes there's one of each appstream id #57

aleixpol opened this issue Jul 27, 2016 · 2 comments

Comments

@aleixpol
Copy link
Collaborator

With the introduction of bundles, it becomes possible to have several versions of the same software available in the system.

API such as:

AsComponent *as_data_pool_get_component_by_id (AsDataPool *dpool, const gchar *id);

Should be returning a list of components. AFAIU.
If we want to have calls to a specific component, we'll have to add more arguments otherwise. If possible.

@ximion
Copy link
Owner

ximion commented Jul 27, 2016

Different versions will always be represented by AsRelease lists - but different bundling origins are something different, I am discussing this with @hughsie for a while.
Additionally to the origin of a component, we IMHO also need an origin_type to determine the bundling system.
I don't know how Snappys "multiple different versions of $stuff" will fit in there, at time this is fundamentally different to how AppStream works - probably the snapd API can solve that by just returning the most recent component / the component whose description should be shown.
In that case, we could get away with origin_type (which Richard calls "prefix" because he determines it by special locations files are installed in - I would like to have a more generic and explicit solution).

@aleixpol
Copy link
Collaborator Author

Different versions might have different metadata. How is the AsComponent built?

@ximion ximion closed this as completed in cde8f1f Aug 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants