[doktor5000@Mageia3 ~]$ rg roccat
roccat-koneplus-1.3.0-4.mga4
roccat-konextd-1.3.0-4.mga4
roccat-tools-1.3.0-4.mga4
[doktor5000@Mageia3 ~]$ rpm -ql roccat-konextd
/usr/bin/konextdconfig
/usr/bin/konextdcontrol
/usr/bin/konextdupdate
/usr/lib/udev/rules.d/90-roccat-konextd.rules
/usr/lib64/roccat/libkonextd.so.1
/usr/lib64/roccat/libkonextd.so.1.3.0
/usr/lib64/roccat/libkonextdwidget.so.1
/usr/lib64/roccat/libkonextdwidget.so.1.3.0
/usr/share/applications/konextdconfig.desktop
/usr/share/man/de/man1/konextdcontrol.1.xz
/usr/share/man/de/man1/konextdupdate.1.xz
/usr/share/man/en/man1/konextdcontrol.1.xz
/usr/share/man/en/man1/konextdupdate.1.xz
[doktor5000@Mageia3 ~]$ ls -al /usr/lib64/roccat/libkonextd*
lrwxrwxrwx 1 root root 19 Feb 5 19:34 /usr/lib64/roccat/libkonextd.so.1 -> libkonextd.so.1.3.0*
-rwxr-xr-x 1 root root 142872 Feb 5 19:33 /usr/lib64/roccat/libkonextd.so.1.3.0*
lrwxrwxrwx 1 root root 25 Feb 5 19:34 /usr/lib64/roccat/libkonextdwidget.so.1 -> libkonextdwidget.so.1.3.0*
-rwxr-xr-x 1 root root 15520 Feb 5 19:33 /usr/lib64/roccat/libkonextdwidget.so.1.3.0*
urpmi roccat-isku roccat-isku-devel
pete910 wrote:May be a note in the rpm package description to state if wanting to have that capability you need to install the dev packages.
Having said that, shouldn't the dev package have the build/config files etc in there too?
doktor5000 wrote:On a related note, sadly only got the Mouse, and also no room for an additional keyboard :/
What bugs me is that even though I've got libnotify installed, I've never seen any notifications.
Will look around for that.
doktor5000 wrote:Development packages usually only contain either source code/headers or libraries,and maybe development-specific documentation.
You may want to look at https://wiki.mageia.org/en/Libraries_policy
Not sure what a proper fix would be, either require the -devel package always, or drop the devel package and move
it's contents to the normal package which would be a bit more ugly IMHO.
cmake -DCMAKE_INSTALL_PREFIX="/usr" -DDEVICES="konextd" ..
pete910 wrote:With regards the notification, if you uninstall the rpm's, build the roccat-tools just for your mouse with
- Code: Select all
cmake -DCMAKE_INSTALL_PREFIX="/usr" -DDEVICES="konextd" ..
then install it you'll see the notify bit and also see what's installed by default for it to work correctly too It's the three that's in the dev package
pete910 wrote:As per link, dev packages like you state have the .h / config files as well as .so's . but the packages don't have them
[doktor5000@Mageia3 ~]$ rpm -q --changelog roccat-tools
* Di Feb 04 2014 doktor5000 <doktor5000@mageia.org>
- own empty /var/lib/roccat with correct permissions
- fix permissions recursively for existing /var/lib/roccat
* Di Feb 04 2014 doktor5000 <doktor5000@mageia.org>
- fixed Requires on roccat-tools for isku subpackage, spotted by pete910
* So Feb 02 2014 doktor5000 <doktor5000@mageia.org>
- new version 1.3.0
o Fixed: KonePure and KonePureOptical macro problems
o Fixed: Actual profile changing twice when using settings tab
o Fixed: Multiple device warnings on replug after firmware update
o Improved: Default profile can now be switched off
o Improved: Sound playback now with per-device configurable volume
o Improved: Sensitivity change now supports audio notifications
o Improved: Shortcut dialog allows toggling modifier checkboxes with key press
o Improved: Profile save dialogs show filename proposition and add extension if needed
o Changed: Device reset now lives in misc menu
* So Feb 02 2014 doktor5000 <doktor5000@mageia.org>
- new version 1.2.0
o Improved: New device scanner with support for future userspace-only implementations
o Fixed: Memory leaks
o Improved: finer grained button inheritance if hardware differs from rmp/rkp
for Kone[+], KoneXTD, KonePure, KonePureOptical, Kova[+], RyosMK*
o Fixed: segfault on first autostart on Mint16
o Fixed: typo in post_install script
o Removed installed development headers
urpmi.addmedia roccat http://mageia.unrealnetworks.co.uk/mga5/x86_64
doktor5000 wrote:No need to repeat yourself, you already mentioned that in the bugreport. Where's the point accusing the user here that "he doesn't get it" ?
The update request is valid, it's up to the maintainer to decide if he updates the package or not. He could even offer it as backport ...
ozky wrote:You don't get it it's having new features so it will break update policy if it's updated to new version.
ozky wrote:Yes i don't need to repeat myself. *snip*
Users browsing this forum: No registered users and 1 guest