https://bugs.kde.org/show_bug.cgi?id=523191
Bug ID: 523191
Summary: Make KWrite separable from Kate (build option or
separate release)
Classification: Applications
Product: kate
Version First unspecified
Reported In:
Platform: unspecified
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: kwrite
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
KWrite and Kate are built and released together from the Kate repository, so
their binaries and .desktop files always ship as one unit. Downstream packagers
and users periodically want one without the other--e.g. Kate installed but
KWrite kept out of the application menu--but there's currently no clean way to
separate them without patching the build.
Would you consider making KWrite separable? Either would help:
- shipping KWrite as its own KDE Gear release/tarball (preferred). or
- a CMake option (e.g. -DBUILD_KWRITE=ON/OFF) and/or separate install
components, so packagers can build/install them independently
Motivation: Kate and KWrite are built and released from a single Kate source
package, so distributions that map one upstream release to one package have no
straightforward way to provide them independently. In nixpkgs, the KDE packages
are produced by an automated generator, so separating KWrite requires a
downstream patch that must be maintained and rebased against every release.
This request recurs across distributions. In nixpkgs it appears as issue
https://github.com/NixOS/nixpkgs/issues/511733 and two separate implementation
attempts, https://github.com/NixOS/nixpkgs/pull/524536 and
https://github.com/NixOS/nixpkgs/pull/543007. Arch tracks it as
https://bugs.archlinux.org/task/75651, and it recurs in user discussions on the
Arch and Manjaro forums at https://bbs.archlinux.org/viewtopic.php?id=279127
and https://forum.manjaro.org/t/hide-kwrite-and-only-use-kate/166477. In each
case the requirement is the same: to install only one of the two applications .
I am raising this upstream because distributions have consistently declined to
carry the split themselves, and understandably so. Arch resolved its report as
won't implement, and the nixpkgs KDE maintainers rejected both pull requests
and directed the request upstream, on the basis that a per-distribution split
amounts to ongoing manual maintenance of what is effectively a wrapper.
Addressed once here, it would apply to every distribution automatically.
As stated above, shipping KWrite as its own KDE Gear release/tarball would be
the cleanest option. Otherwise, a build option such as -DBUILD_KWRITE=ON/OFF
could also suffice.
--
You are receiving this mail because:
You are watching all bug changes.
