Package Details: kalu 4.5.2-2

Git Clone URL: https://aur.archlinux.org/kalu.git (read-only, click to copy)
Package Base: kalu
Description: Upgrade notifier w/ AUR support, watched (AUR) packages, news
Upstream URL: https://github.com/Thulinma/kalu
Licenses: GPL3+
Submitter: jjacky
Maintainer: Thulinma
Last Packager: Thulinma
Votes: 184
Popularity: 1.15
First Submitted: 2012-02-14 18:03 (UTC)
Last Updated: 2024-09-15 21:24 (UTC)

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 Next › Last »

justin8 commented on 2013-07-16 06:21 (UTC)

Can you please add arch='armv7h' as well? Tested on a samsung chromebook and it is working perfectly.

sir_sure commented on 2013-06-04 21:03 (UTC)

I see, seems like I haven't grasped Kalu's philosophy until now. What I would like to have is an icon show up in the systray and a libnotify notification pop up at every session start (i.e. after fresh boot), but only if there are actually updates available (given that we are Arch users this happens fairly frequently ;-) ). The reason for this is that I usually only do system upgrades immediately after booting, so I wouldn't rely on Kalu being there for me all the time :-) But, as I already mentioned, it seems like I wasn't aware of Kalu's purpose yet. Given the wealth of its features, maybe it is a bit too much of an overkill for my purpose. A simple script will probably suffice. Anyways, thank you very much for your neat work and efforts! The comprehensive yet very concise man pages deserve a special mention at this point.

jjacky commented on 2013-06-03 13:40 (UTC)

Seems you're trying to use kalu only "on demand" to do a sysupgrade, but that's not really what it was designed for. Meaning, it is first an upgrade notifier, that does indeed sit in your systray all day long, checking for upgrades and notifying when there are any every once in a while. That's the idea, so quitting after a check or after running a sysupgrade wouldn't really be useful then. If you wanna use kalu for a one-shot operation, you could run `kalu -a` though that is CLI-only. I'm not sure doing a GUI equivalent would be worth it, because kalu needs to stay alive as long as the notifications are (so it can handle the clicks on action-buttons), and again, having it quit right after feels somewhat "odd" and against the idea to me...

sir_sure commented on 2013-06-03 12:56 (UTC)

Cool app! It would be great if there was an option which would allow automatically quiting kalu once a system update is done. Of course you could also do that by running a script after an update (which is already possible), but a solution not involving kill would be cleaner. Also, an option preventing Kalu from starting if there are no updates available would be cool so that after auto-starting Kalu on session login it would not start and linger in the notification area. Anyways, thank you for writing Kalu!

moonman commented on 2013-06-02 09:37 (UTC)

Thank you

jjacky commented on 2013-06-01 17:20 (UTC)

Yeah, sounds like a good idea. I'll see to do that, thanks.

moonman commented on 2013-06-01 06:24 (UTC)

I agree, but you could probably change the group of "wheel" to let's say "kalu", include the file and just document that users would need to add themselves to group "kalu" in order to get rid of passwod-asking. Seems a little easier than messing with these polkit policies. Not trying to force anything on you though, just a friendly suggestion. I appreciate the great application you've created.

jjacky commented on 2013-05-31 16:31 (UTC)

This is a nice tip, thanks. I know some people might be interested in this, so I'll add it to the man page or something; but I'm not sure I wanna add the file as part of the package. I mean, a sysupgrade remains an important and possibly critical operation in how it can affect one's system, so I think by default it should require user authentication.

moonman commented on 2013-05-31 11:23 (UTC)

would it be possible to add /etc/polkit-1/rules.d/20-kalu.rules with this in it: polkit.addRule(function(action, subject) { if ((action.id == "org.jjk.kalu.sysupgrade") && subject.isInGroup("wheel")) { return polkit.Result.YES; } }); so the users of group wheel wouldn't be prompted for the password. Thank you

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 Next › Last »