In D5534#89316, @JoshStrobl wrote:

Why are we no longer building the plugins? Were they removed entirely? Is there another blocker for enabling them?
If they were deprecated entirely, you haven't sent a PR to getsolus/solus-sc to update the repo_data for the obsoleting.

We are no longer building them because they don't exist. digiKam now uses a dedicated plugin interface instead, more powerful than KIPI stuff. More information will be published at next 6.1.0 release, but for now they are gone. I don't know how to send a PR to getsolus/solus-sc to update the repo_data for the obsoleting, have you some documentation on how to do this?

Regarding the missing docs this is a known issue (I believe it was forgotten about when the tarballs were created upstream), and is due to be fixed and reinstated in the next release 6.1.0. Can you suggest a method on how to deal with this?

Could I leave the pattern for the digikam-docs in place and ship an empty package, or maybe comment it out with an explanation as to why it is expected back in 6.1.0?

In D5534#90407, @clivejo wrote:

In D5534#89316, @JoshStrobl wrote:

Why are we no longer building the plugins? Were they removed entirely? Is there another blocker for enabling them?
If they were deprecated entirely, you haven't sent a PR to getsolus/solus-sc to update the repo_data for the obsoleting.

We are no longer building them because they don't exist. digiKam now uses a dedicated plugin interface instead, more powerful than KIPI stuff. More information will be published at next 6.1.0 release, but for now they are gone. I don't know how to send a PR to getsolus/solus-sc to update the repo_data for the obsoleting, have you some documentation on how to do this?
Regarding the missing docs this is a known issues, and is due to be fixed and reinstated in the next release 6.1.0. Can you suggest a method on how to deal with this?
Could I leave the pattern for the digikam-docs in place and ship an empty package, or maybe comment it out with an explanation as to why it is expected back in 6.1.0?

Regarding the repo_data, the steps are:

1. Fork https://github.com/getsolus/solus-sc
2. Add an entry in repo_data/distribution.xml.in
3. cd into repo_data and run the merged_repos.sh script. It'll generate the distribution.xml
4. Do a PR.

If the docs are broken and the plugin bits are needing more details, I'd rather we wait until 6.1.0.