Search Criteria
Package Details: kalu-kde 4.5.2-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/kalu-kde.git (read-only, click to copy) |
---|---|
Package Base: | kalu-kde |
Description: | Upgrade notifier w/ AUR support, watched (AUR) packages, news; supports autohide in KDE Plasma's panel |
Upstream URL: | https://github.com/Thulinma/kalu |
Licenses: | GPL3+ |
Conflicts: | kalu |
Provides: | kalu |
Submitter: | Rhinoceros |
Maintainer: | Thulinma (jghodd) |
Last Packager: | Rhinoceros |
Votes: | 14 |
Popularity: | 0.000002 |
First Submitted: | 2014-12-30 12:30 (UTC) |
Last Updated: | 2024-09-14 14:24 (UTC) |
Dependencies (11)
- curl (curl-http3-ngtcp2AUR, curl-gitAUR, curl-c-aresAUR)
- dbus (dbus-gitAUR, dbus-selinuxAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classicAUR)
- libnotify (libnotify-gitAUR)
- notification-daemon (xfce4-notifyd-layer-shell-gitAUR, awesome-luajitAUR, awesome-gitAUR, awesome-luajit-gitAUR, dunst-gitAUR, twmn-gitAUR, lxqt-notificationd-gitAUR, rofication-gitAUR, xfce4-notifyd-gitAUR, dunst-wayland-gitAUR, enlightenment-gitAUR, enlightenment-git-asanAUR, swaync-gitAUR, awesome, dunst, lxqt-notificationd, mate-notification-daemon, notify-osd, xfce4-notifyd)
- pacman (pacman-gitAUR)
- polkit (polkit-gitAUR, polkit-consolekitAUR)
- statusnotifierAUR (statusnotifier-introspection-dbus-menuAUR)
- groff (groff-gitAUR) (make)
- perl (perl-gitAUR) (make)
Latest Comments
1 2 3 4 5 6 .. 14 Next › Last »
Rhinoceros commented on 2024-12-31 05:41 (UTC)
Hi all, just letting you know that I've finally decided to stop using kalu, and I've migrated to a bunch of shell scripts instead. These work perfectly fine, and are extremely lightweight. They are slightly fiddly to install, although I've written up instructions for KDE. The scripts don't have much of the functionality of kalu, but they do the two main tasks I need. They notify when updates are available, and can trigger upgrades in a terminal emulator.
The advantage of the scripts is that they are extremely simple, so easy to maintain in the future. I'll disown kalu-kde now. Best of luck in the future, and thank you Thulinma and jghodd for all the help with this package in the past.
BluePyTheDeer251 commented on 2024-10-05 16:32 (UTC) (edited on 2024-10-05 16:43 (UTC) by BluePyTheDeer251)
Sorry to ask, but what does MIA mean? (idk most terminology here)
nvm it apparently means "missing in action"
Rhinoceros commented on 2024-10-05 06:01 (UTC)
Thanks @Aerion. FWIW I've submitted an orphan request for statusnotifier since jjacky is MIA. I have no plans for long-term maintenance, but I can at least apply the fix from the comments.
BluePyTheDeer251 commented on 2024-10-01 17:19 (UTC) (edited on 2024-10-05 16:52 (UTC) by BluePyTheDeer251)
Thanks, will use once I get home
Edit: Used it like 2 days ago (the "proper" way), and it just works™.
Aerion commented on 2024-10-01 15:44 (UTC) (edited on 2024-10-01 15:45 (UTC) by Aerion)
@BluePyTheDeer251 The solution is mentioned in the comments for statusnotifier. It can be solved as follows:
The 'quick and dirty' way:
sudo pacman -S --asdeps gobject-introspection
Then install statusnotifier as normal.
The 'proper' way:
makedepends=('gobject-introspection')
BluePyTheDeer251 commented on 2024-09-22 23:01 (UTC)
Tried to install, couldn't because of statusnotifier failing to build.
Rhinoceros commented on 2024-09-14 14:25 (UTC)
I just bumped the pkgrel, since this package will need to be rebuilt for pacman 7. Just uninstall
kalu-kde
, do the pacman update, then reinstallkalu-kde
. Everything seems to work fine for me with pacman 7.Thulinma commented on 2024-04-01 22:11 (UTC)
There was a second occurrance of the same bug I fixed the other day... which I fixed earlier today. There should be no more crashes at all with 4.5.2! Please let me know if anyone still experiences any 😭
jghodd commented on 2024-04-01 21:37 (UTC)
@Rhinoceros - i get what you're saying. i'll take another look at the syntax and see if i can use sed to strip out the optimization and source-fortification.
Rhinoceros commented on 2024-03-31 23:33 (UTC)
Thanks @jghodd that looks good. I had another thought, and I'm not sure if my original idea was a bit faulty.
What if users had their CFLAGS as
-O3
, say? It's probably more robust to explicitly append-O0
instead of assuming users have-O2
.I couldn't find much documentation on
-Wp,-D_FORTIFY_SOURCE=2
though, so I'm not sure what the default replacement is.1 2 3 4 5 6 .. 14 Next › Last »