Erick555

I think making an Sdk extension for one app to consume may be questionable especially if you are making a separate [stub app extension](https://github.com/flathub/flathub/pull/3014) to use this one. Just merging...

> It usually has to start somewhere, there are more and more separate Qt components showing up on flathub, which could be reused from the Sdk extension. Like which ones?...

> Qt Creator does not require any Qt forks, where did you get that from? Which apps require Qt forks? The KDE ones perhaps yeah, sorry it was llvm fork...

See https://github.com/flathub/flathub/pull/3013#issuecomment-1100066897

Then it absolutely can't be an extension. Extensions are optional by flatpak design. You can either bundle it or make a baseapp. Or even better ask for adding missing modules...

There are better ways to solve the problem. You chose one that doesn't fit. This is my point.

Ok, that's fine. Let's hear opinion from others.

There is also stability concern regarding to this one as in current form it's going to ship always latest Qt 6.x release and some apps/tools using it may need adjustments...

Mentioned use case is exactly why it was [rejected](https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/356#note_98819362) in the past so things are going in circle here: > Using an SDK extension for dependencies is a really really...

This opinion was from flathub organization [member](https://github.com/orgs/flathub/people). All I tried is to convince you are wasting your time but somewhat you think I'm wasting it which is quite irony. Anyway...