Description of problem: Thank you for maintaining Kitty on Fedora! :-) The kitty package on Fedora installs /etc/profile.d/kitty.sh, which enables shell integration even if the user hasn't modified their kitty.conf to enable it. And if the user has explicitly disabled shell integration in their kitty.conf, it remains enabled without the user knowing why or how. Obviously the addition of this file was intended to be helpful, but I think this is a case where it would be better to leave this to the user and not do something surprising. 1. Kitty's documentation is simple and clear on how to enable shell integration, and without reading the documentation the user wouldn't know how to use the shell integration anyway. 2. kitty.conf is where users expect to be able to configure Kitty. They would have to know that the packager has decided to install a file that auto-enables Kitty's shell integration outside of kitty.conf. (Principle of least surprise and all that.) 3. From what I can see, Ubuntu, OpenSUSE and Arch Linux don't install a similar file. Arch Linux has a separate kitty-shell-integration package but that doesn't actually auto-enable shell integration, it just installs the /usr/lib/kitty/shell-integration files. Thank you! Version-Release number of selected component (if applicable): Name : kitty Version : 0.24.4 Release : 1.fc35 Architecture : x86_64
Thanks for reporting. I wanted as well to made separate sub-packages for shell integrations and they should disabled by default IMO. Hope @zawertun could help with fix due lack of time now.
Wow, thanks for the very prompt reply Artem! No worries, I know the feeling. I don't think there's a good reason to move /usr/lib/kitty/shell-integration files into a subpackage or multiple subpackages. Ubuntu and OpenSUSE don't do that. So from my perspective this is just about kitty.sh and kitty.fish, which are files only Fedora is installing. Personally I think the solution is as simple as removing kitty.fish and kitty.sh from the package. If you want to keep them then I attached a patch, though I'm dubious about their value. (I'm a Fedora packager, but stepped away from all but one package a few years ago and I'm not currently interested in getting back into maintenance/co-maintenance!) I can see from commit history that zawertun had to revert auto-enabling ZSH integration. I think all of this should just be left to the user :-)
Created attachment 1865385 [details] Patch for subpackages
FEDORA-2022-a92544aa9c has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a92544aa9c
FEDORA-2022-a92544aa9c has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-27a289eaa6 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-27a289eaa6
FEDORA-2022-d2c9637537 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d2c9637537
Thanks very much Artem :-)
*** Bug 2053975 has been marked as a duplicate of this bug. ***
Thanks Everyone!
FEDORA-2022-d2c9637537 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-d2c9637537` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d2c9637537 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-27a289eaa6 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-27a289eaa6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-27a289eaa6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-d2c9637537 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-27a289eaa6 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.