Package Details: kalu 4.3.0-1

Git Clone URL: https://aur.archlinux.org/kalu.git (read-only)
Package Base: kalu
Description: Upgrade notifier w/ AUR support, watched (AUR) packages, news
Upstream URL: https://jjacky.com/kalu
Licenses: GPL3+
Submitter: jjacky
Maintainer: jjacky
Last Packager: jjacky
Votes: 182
Popularity: 1.159299
First Submitted: 2012-02-14 18:03
Last Updated: 2018-06-04 17:45

Latest Comments

« First ‹ Previous ... 4 5 6 7 8 9 10 11 12 13 14 Next › Last »

jjacky commented on 2013-06-03 13:40

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

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

Thank you

jjacky commented on 2013-06-01 17:20

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

moonman commented on 2013-06-01 06:24

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

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

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

adam777 commented on 2013-04-05 05:32

And now that pacman 4.1 is out on [stable], please update Kalu to support it.

bayi commented on 2013-04-01 23:52

nevermind i found the PKGBUILD on your site.... my brain was in write only mode again

bayi commented on 2013-04-01 23:51

Hi i saw on your site that there is already an updated version for pacman 4.1 +
Can you please update the PKGBUILD or, upload a new package that works with the new pacman ? I miss kalu since i updated today ( yes im on testing ... )