It looks like this package has been abandoned its developer.
Version 1.2 is the last/latest version available, however, so I have removed the out-of-date flag.
When compiled from source, this package works fine with KDE 4.12, so I have created an SVN version of this package at https://aur.archlinux.org/packages/kdeplasma-applets-keyleds-svn/
This (non-SVN) package will not be updated by me unless development resumes upstream.
Search Criteria
Package Details: kdeplasma-applets-keyleds 1.2-1
Package Actions
| Package Base: | kdeplasma-applets-keyleds |
|---|---|
| Description: | KDE4 KeyLEDs - Plasma(plasmoid) Keyboard Status LEDs |
| Upstream URL: | http://software.dukitan.com/en/keyleds/ |
| Category: | kde |
| Licenses: | |
| Submitter: | ilpianista |
| Maintainer: | Aerion |
| Last Packager: | None |
| Votes: | 7 |
| First Submitted: | 2013-10-15 16:29 |
| Last Updated: | 2013-10-15 16:29 |
Dependencies (2)
Required by (0)
Sources
Latest Comments
Comment by Aerion
Comment by petaramesh
Broken in KDE 4.12, as Unikum said 9 months ago. Is this maintained ?
Comment by unikum
Can't get it work in the KDE 4.10. After add widget on the panel I get message: Unknown widget.
Comment by laracraft93
startdir contains the absolute path to the directory where the PKGBUILD file is located. This variable used to be used in combination with /src or /pkg postfixes, but the use of srcdir and pkgdir variables is the modern method. $startdir/src is not guaranteed to be the same as $srcdir, and likewise for $pkgdir. Use of this variable is deprecated and strongly discouraged.
pkgdir points to the directory where makepkg bundles the installed package, which becomes the root directory of your built package.
https://wiki.archlinux.org/index.php/Creating_Packages
Comment by ilpianista
please rename this package following the KDE package guidelines,
https://mailman.archlinux.org/pipermail/aur-general/2012-July/019567.html
Thanks
Anonymous comment
By Questions ;)
1. My fault. I do not worry about this issue.
2. I'm not really sure how. Even though the developer of the software binary. The only thing I can guarantee is based on trust in myself and in hosting the official repository of binary software.
Thanks for the tip of the PKGBUILD.
Comment by raku
1. Your PKGBUILD isn't ready for x86_64 systems.
2. Binary packages from untrusted mirrors are IMO not secure. Can you guarantee that yours is safe and you are not selling me any backdoors in it?
Here's the PKGBUILD for SVN version: http://aur.pastebin.com/m4ve7ZyY
Anonymous comment
Do not particularly like being compiling software, I like to get the package ready for installation.
The source is available in the repository, see http://software.dukitan.com/en/keyleds
Comment by raku
Why PKGBUILD uses binary instead of building from sources?