search

flathub-infra / documentation

Documentation for flathub
https://docs.flathub.org/
36 stars 35 forks source link

extensions/plugins #22

Closed Lonsfor closed 9 months ago

Lonsfor commented 1 year ago

There should be something that explains how they work in flathub

How are they different from regular apps? What requirements do they have? What do normal apps require to integrate them? Do they need to go thought the normal submission process?

TheEvilSkeleton commented 1 year ago

Just a heads up, I've already partially worked on this on https://github.com/flatpak/flatpak-docs/pull/349, but I'll have to carry over the work at some point.

razzeee commented 1 year ago

Do you want any help with that?

TheEvilSkeleton commented 1 year ago

Yes, I can't really explain merge-dirs https://github.com/flatpak/flatpak-docs/pull/349#discussion_r940799683

hfiguiere commented 1 year ago

merge-dirs list directories from the top-level of the extension to be "merged" into the corresponding top-level of the extension point.

The merge is done by making symbolic links into the extension.

Directories are separated by ;

One example is for audio plugins. Where the lv2 directory of the xtension will be merged in the lv2 directory of the extension point where the app will locate the plugins (same with vst3, vst, ladspa and clap).

bbhtt commented 11 months ago

I covered most of it in https://github.com/flatpak/flatpak-docs/pull/419. There's not much specific to Flathub in terms of submitting extensions other than they should follow the same guidelines and requirements and always use branch/foo on GitHub in case they correspond to an API/ABI stable version. Also use a flathub.json to skip icon check, can skip the validation here https://docs.flathub.org/docs/for-app-authors/appdata-guidelines/#use-flathubs-appstream-util and must install an appdata file to show up on the frontend.

If anyone knows anything else that needs to be added, please comment below.

If that's merged, I'll add a few lines somewhere.