Maybe you could try something like https://invent.kde.org/sysadmin/binary-factory-tooling/-/blob/master/craft/enabled-projects.yaml#L289 to force rebuilds of your unreleased software.

cfitsio now builds, my craft was outdated.

If a static lib is used all its dependent libs must be linked too. Ideally the libcfitsio.pc would provide the required libs.
Now why do you build libcfitsio static? I tried to build it locally, it tires to build shared and fails due to the curl issue you had before.

I just fixed the issues unrelated to debug suffixes.
The debug build is green https://binary-factory.kde.org/view/Management/job/Craft_Build_Master_Cache_windows-msvc2019_64-cl-debug/

1 sounds great.
But we can't enforce it because every maintainer manually uploads the stuff to the store.

Yes I think when a maintainer is preparing a Windows store release, they should also preserve the other artifacts.
That way we would also publish the nsis installer and the plain archives.

The issue was introduced recently I currently rebuild the cache to fix the issue, it should be gone in the next couple of days.

In T9579#250279, @andriusr wrote:

Hi, I was an avid user of Dolphin on KDE4 times, I'd like to share some thoughts ...

My main use case was browsing remote (sftp) files and opening them in Kate. Since at that time all the KDE environment was shared (plug-ins, kio etc.) it was fantastic to work that way! So, first of all, for Dolphin and for other apps I think we should always ship them with a common set of KIOs. I understand that individual app installers are the new way since KF5, but maybe we could think about packaging some sets of apps as a bundle.

In D25119#676781, @cullmann wrote:

Hmm, I don't think you need a theme chooser, we just need to watch for the palette change signal and then trigger again the theme name setting based on the background palette.
That would be enough to detect bright/dark mode.

And change those during runtime....

Yea my idea didn't make much sense.
Reading your comment I realized that we should probably implement a theme chooser in a kf5 and provide the themes as plugins, that way we could also provide other themes, not just breeze.

I love it.
Could we add a option to the exported target, so that you can basically always link that library with out an effect, until a cmake flag is set?
This way we can bring it to all applications and enable it from craft.
-DENABLE_BREEZE_BINARY_THEME=ON (or what ever)

We also need to add detection for virtual windows files to kio, tries to doewnload all files in onedrive/owncloud when the home dir is entered, to index them.

Draggin and dropping files from 7z to dolphin fails as the prompt move/copy here doesn't lock the files and the tmp files are gone when the user decides.

I guess we should see KDE as a brand here and offer the native KDE icons and a breeze theme :)

In T9575#244277, @mgallien wrote:

Is somebody already working on packaging Dolphin for the Windows Store ?

I have tested the current builds on my work laptop and they seem to work fine and do the job (I had crashes with a previous version).

https://invent.kde.org/packaging/craft-blueprints-kde/commit/162d3fe1b03901658c0ca56a2ee7d14430f3f255

It probably won't hurt

You could also just deploy the binary with msys.