[PRQ#57560] Deletion Request for kate-root
MarsSeed [1] filed a deletion request for kate-root [2]: Currenty broken. But also completely unneeded. Repo's kate fully supports prompting the user for root write access, and also can open files via the admin:// protocol (if extra/kio-admin package is installed). [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/kate-root/
MarsSeed [1] filed a deletion request for kate-root [2]:
Currenty broken. But also completely unneeded.
Repo's kate fully supports prompting the user for root write access, and also can open files via the admin:// protocol (if extra/kio-admin package is installed).
I just saw that this same package has already been deleted 6 months ago: - PRQ#46797: https://lists.archlinux.org/hyperkitty/list/aur-requests@lists.archlinux.org...
If broken please report in the comments, that is what they are for; I actually have fixed it recently. I maintain the package, and I use and need it. "totally unneeded" I want to refute, since "official" kate refuses to run as root (and for me also under sudo!). If you thin "totally uneeded", please argue why. With the recent change to Qt6/ kf6 I have not followed yet, since it is a major change and I am at travel now and do not want to break my system with a major upgrade. I will come back to it later. Please do not accept the deletion request. On Sat, 09 Mar 2024 23:19:40 +0000, notify@aur.archlinux.org wrote:
MarsSeed [1] filed a deletion request for kate-root [2]:
Currenty broken. But also completely unneeded.
Repo's kate fully supports prompting the user for root write access, and also can open files via the admin:// protocol (if extra/kio-admin package is installed).
[1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/kate-root/
I maintain the package, and I use and need it.
You don't need it.
"totally unneeded" I want to refute, since "official" kate refuses to run as root (and for me also under sudo!).
That's by design. Don't try to run it as root.
If you thin "totally uneeded", please argue why.
I have already done so:
Repo's kate fully supports prompting the user for root write access, and also can open files via the admin:// protocol (if extra/kio-admin package is installed).
Non-root Kate can do everything a root Kate would be able to do. If you opened a file with read-only access, upon saving, it will prompt you for root credentials. If you want to open something for which your user doesn't have read access, you need to install the 'kio-admin' package from the repo. And then open that directory or file with the admin:// protocol. E.g., the following directory is only accessible (readable/traversable) by root: /etc/NetworkManager/system-connections/ Open it by entering the following path in Kate's Open File dialog: admin:///etc/NetworkManager/system-connections/ Hope it helps! Cheers Marcell / MarsSeed
On Sun, 10 Mar 2024 02:36:22 +0100, Marcell Meszaros <marcell.meszaros@runbox.eu> wrote:
Repo's kate fully supports prompting the user for root write access, and also can open files via the admin:// protocol (if extra/kio-admin package is installed).
Non-root Kate can do everything a root Kate would be able to do. If you opened a file with read-only access, upon saving, it will prompt you for root credentials.
For me not. Maybe if used within a full-fledged KDE environment. I use kate as a standalone editor without using a KDE environment, nor a gnome environment, but a simple window manager without any desktop envitronment. For me it simpky refuses to save with the message
The document could not be saved, as it was not possible to write <filename>. Check that you have write access to this file or that enough disk space is available.
If you want to open something for which your user doesn't have read access, you need to install the 'kio-admin' package from the repo. And then open that directory or file with the admin:// protocol.
E.g., the following directory is only accessible (readable/traversable) by root:
/etc/NetworkManager/system-connections/
Open it by entering the following path in Kate's Open File dialog:
admin:///etc/NetworkManager/system-connections/
Wow. That is much manual overhead. I usually work at the terminal and type `kate <filename>`. So, still, kate does _not_ allow to be a editor for simple root usage, like `gedit` allows, like `medit` allows, like `mcedit` allows. I still see valid use cases for this package and I continue to provide it.
Non-root Kate can do everything a root Kate would be able to do. If you opened a file with read-only access, upon saving, it will prompt you for root credentials.
For me not.
Maybe if used within a full-fledged KDE environment.
One does not need a full KDE desktop, only Kate's direct dependencies, which include kio. Then the 'kio-admin' package can be installed and Kate will support admin://.
If you want to open something for which your user doesn't have read access, you need to install the 'kio-admin' package from the repo. And then open that directory or file with the admin:// protocol.
E.g., the following directory is only accessible (readable/traversable) by root:
/etc/NetworkManager/system-connections/
Open it by entering the following path in Kate's Open File dialog:
admin:///etc/NetworkManager/system-connections/
Wow. That is much manual overhead.
I usually work at the terminal and type `kate <filename>`.
I don't think it's much overhead. Simply open the file with something like: `kate admin://$(pwd)/filename` You can define an alias function for kate in your shell, and then you can also use the same syntax you already do, `kate filename`. (Or you can make different alias if you want to differentiate, like `kater` for root.) Keeping a root-patched duplicate build on AUR really seems like an overkill, and unnecessary. Also Arch Wiki mentions how it is an anti-pattern to run full GUI applications as root, and lists all the alternative ways of achieving the same goal without such a measure. You can run whatever software you want, but please don't keep this on AUR. It seems you are the only person who uses it. Cheers, Marcell / MarsSeed
You might also need to install 'polkit-kde-agent' for supporting the root password dialog.
OK I give the decision if it should be deleted or not to the AUR maintainers, and I will respect the decision if it is for deletion. (I have not been the maintainer of the previously deleted one, so I do not know the arguments there; as far as I know it had build issues.) The package has been updated to 24.02.0 and kf6 and for me it did build and works. Issues with packaging should be reported in comments. I am not sure if I am the only one using it; I got out of date notification from someone recently which is a hint that it is not only me using it. When doing "root" stuff I usually directly do it from my always-open root shell (it is a single user machine anyway) and I do not use any sudo or so generally. Regards! On Sun, 10 Mar 2024 15:09:02 +0100, Marcell Meszaros <marcell.meszaros@runbox.eu> wrote:
Non-root Kate can do everything a root Kate would be able to do. If you opened a file with read-only access, upon saving, it will prompt you for root credentials.
For me not.
Maybe if used within a full-fledged KDE environment.
One does not need a full KDE desktop, only Kate's direct dependencies, which include kio.
Then the 'kio-admin' package can be installed and Kate will support admin://.
If you want to open something for which your user doesn't have read access, you need to install the 'kio-admin' package from the repo. And then open that directory or file with the admin:// protocol.
E.g., the following directory is only accessible (readable/traversable) by root:
/etc/NetworkManager/system-connections/
Open it by entering the following path in Kate's Open File dialog:
admin:///etc/NetworkManager/system-connections/
Wow. That is much manual overhead.
I usually work at the terminal and type `kate <filename>`.
I don't think it's much overhead. Simply open the file with something like:
`kate admin://$(pwd)/filename`
You can define an alias function for kate in your shell, and then you can also use the same syntax you already do, `kate filename`. (Or you can make different alias if you want to differentiate, like `kater` for root.)
Keeping a root-patched duplicate build on AUR really seems like an overkill, and unnecessary.
Also Arch Wiki mentions how it is an anti-pattern to run full GUI applications as root, and lists all the alternative ways of achieving the same goal without such a measure.
You can run whatever software you want, but please don't keep this on AUR. It seems you are the only person who uses it.
Cheers, Marcell / MarsSeed
Request #57560 has been Rejected by muflone [1]: as long the package is maintained and working there's no reason to delete it [1] https://aur.archlinux.org/account/muflone/
participants (4)
-
dreieck
-
Marcell Meszaros
-
notify＠aur.archlinux.org
-
oid-maps＠seznam.cz