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

Stabilize AppstreamCompose API #628

Open
tytan652 opened this issue Apr 24, 2024 · 2 comments
Open

Stabilize AppstreamCompose API #628

tytan652 opened this issue Apr 24, 2024 · 2 comments

Comments

@tytan652
Copy link
Contributor

tytan652 commented Apr 24, 2024

I thought it was stable since the compose API was promoted on documentations but the I_KNOW_THE_APPSTREAM_COMPOSE_API_IS_SUBJECT_TO_CHANGE thing indicate the opposite.

If prioritizing the API over the cli tools is really preferred, why keeping this dealbreaker ?

Or they are stuff that needs to be worked on before ?

@ximion
Copy link
Owner

ximion commented Apr 26, 2024

I am still not happy with it, the API is leaking a few internals for appstream-generator to hook into that could probably be abstracted away better.
If you only use the AscCompose class (and not things like AscCanvas) you most likely won't experience much, or any, breakage though.

Ideally I would have more time to work on asgen and the compose library to declare it fully stable, but I currently don't have that time (or funding) sadly.

What do you want to use the API for / what concerns do you have?

@tytan652
Copy link
Contributor Author

What do you want to use the API for / what concerns do you have?

I was trying to see how feasible it was to replace the use of appstreamcli compose in flatpak-builder, but this kind of thing blocks the idea.

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