Change Details

The repo https://invent.kde.org/sdk/kdesdk-kioslaves currently only holds one software component, kio_perldoc. Once ported to WorkerBase (planning a MR this late afternoon), the repo name no longer matches. Similar to how repo "zeroconf-ioslave" was renamed to "kio-zeroconf" to adapt to the porting (see T15662) the repo name (and resulting release tarball names) ideally would be changed as well. Question for the start: what name to pick? "kio-extras-sdk", to follow the old repo idea to hold multiple things of the sdk domain related to kio? "kio-perldoc", to match the reality there is just one kio slave (soon worker)? Something else? (And yes, there could also be a meta-discussion whether each software component should be in its own separate repo, or all related bundled in big repos, trying not to go into that discussion here :) )

The repo https://invent.kde.org/sdk/kdesdk-kioslaves currently only holds one software component, kio_perldoc. Once ported to WorkerBase (see MR https://invent.kde.org/sdk/kdesdk-kioslaves/-/merge_requests/2), the repo name no longer matches. Similar to how repo "zeroconf-ioslave" was renamed to "kio-zeroconf" to adapt to the porting (see T15662) the repo name (and resulting release tarball names) ideally would be changed as well. Question for the start: what name to pick? "kio-extras-sdk", to follow the old repo idea to hold multiple things of the sdk domain related to kio? "kio-perldoc", to match the reality there is just one kio slave (soon worker)? Something else? (And yes, there could also be a meta-discussion whether each software component should be in its own separate repo, or all related bundled in big repos, trying not to go into that discussion here :) )

The repo https://invent.kde.org/sdk/kdesdk-kioslaves currently only holds one software component, kio_perldoc. Once ported to WorkerBase (planning a MR this late afternoonsee MR https://invent.kde.org/sdk/kdesdk-kioslaves/-/merge_requests/2), the repo name no longer matches. Similar to how repo "zeroconf-ioslave" was renamed to "kio-zeroconf" to adapt to the porting (see T15662) the repo name (and resulting release tarball names) ideally would be changed as well. Question for the start: what name to pick? "kio-extras-sdk", to follow the old repo idea to hold multiple things of the sdk domain related to kio? "kio-perldoc", to match the reality there is just one kio slave (soon worker)? Something else? (And yes, there could also be a meta-discussion whether each software component should be in its own separate repo, or all related bundled in big repos, trying not to go into that discussion here :) )