Closed whot closed 1 year ago
libportal is not API nor ABI stable, so I'd be okay with breaking API for the next stable release.
For now, I guess a _full
variant of this function should be enough
libportal is not API nor ABI stable, so I'd be okay with breaking API for the next stable release.
Has that been the case always? If that's the case, how can libportal be suitable for any application that intends to be both distributable via Flatpak and traditional distributions?
Has that been the case always?
That's how I've been approaching libportal development since at least 2021 :slightly_smiling_face:
If that's the case, how can libportal be suitable for any application that intends to be both distributable via Flatpak and traditional distributions?
Personally, I consider libportal suitable for Flatpak applications only... somewhat like a Rust / cargo dependency, you have to pinpoint the exact version you want in the manifest.
Renamed to _full
and tests updated and one extra new test added, should be ready.
That's how I've been approaching libportal development since at least 2021 🙂
That is not what I would have assumed. Anyway, filed https://github.com/flatpak/libportal/issues/129.
Same as the ScreenCast API
Fixes #127
cc @jadahl
Marking as Draft until I've sold off the right to rename this to a more sensible function name to the highest bidder. Any suggestions?