Roccat-Tools 3.1.0 is out. http://sourceforge.net/p/roccat/news/2015/02/roccat-tools-310/
why so slow?
Well you see, this is volunteer-based process, and no one is paid for this. Also personal things take priority, for instance when my baby is ill I'm not gonna look into this - and she is ill now. Feel free to add a ebuild yourself - or consider donations!
promote me to maintainer of this package.
This package is maintained by proxy-mainteiners. http://wiki.gentoo.org/wiki/Project:Proxy_Maintainers
I came across this rather by chance, but having done so. (In reply to Dmitry Pisklov from comment #2) > Well you see, this is volunteer-based process, and no one is paid for this. > Also personal things take priority, for instance when my baby is ill I'm not > gonna look into this - and she is ill now. > Feel free to add a ebuild yourself - or consider donations! That was most uncalled for <maintainer> <email>dpisklov@gmail.com</email> <name>Dmitry Pisklov</name> <description>Proxy maintainer. Assign bugs to him</description> </maintainer> <maintainer> <email>perfect007gentleman@gmail.com</email> </maintainer> You asked for it. Shoot a bumped ebuild in full or in a patch. I can then commit this to metadata.xml. Until then, no. Whether you 2 can contribute in a collaborative manner is another mystery.
Created attachment 398414 [details] New ebuild
Created attachment 398416 [details, diff] Patch for /usr/portage/profiles/desc/input_devices.desc
~/cvsPortage/gentoo-x86/sys-apps/roccat-tools $ sudo ebuild roccat-tools-3.1.0.ebuild clean install >>> Completed installing roccat-tools-3.1.0 into /mnt/gen2/TmpDir/portage/sys-apps/roccat-tools-3.1.0/image/ perfect. Well done. There are now 6 versions of roccat-tools. Can you nominate those that can be purged from portage? Old versions need be stopped from piling up. I am holding off adding it until a reply to this. NB: While "Feel free to add a ebuild yourself - or consider donations!" was uncalled for, so also was "why so slow?". Smacks of out outright impatience, it had been 'all' of 3 days. It invited a retort and sure enough it came. The health of the baby is without question of primary importance. Also, consider whether you want a version to be made stable. At this point in time, -2.4.0 or earlier qualify
@Ian, 2.4.0 is stable (and can be marked as such), everything up to 2.4.0 can be purged. Thanks
~/cvsPortage/gentoo-x86/sys-apps/roccat-tools $ l *.ebuild roccat-tools-2.0.0.ebuild roccat-tools-2.2.0.ebuild roccat-tools-3.0.0.ebuild roccat-tools-2.1.0.ebuild roccat-tools-2.4.0.ebuild roccat-tools-3.1.0.ebuild stable upstream has a different meaning all together within the gentoo project. ~/cvsPortage/gentoo-x86/sys-apps/roccat-tools $ grep KEYWORDS ./* yields grep: ./CVS: Is a directory grep: ./files: Is a directory and :KEYWORDS="~amd64 ~x86" for all ebuilds means all these versions are testing. stable is denoted by KEYWORDS="amd64 x86" and requires testing by the arch teams. There are docs in the gentoo wiki that describe this. It's not essential. *roccat-tools-3.1.0 (10 Mar 2015) 10 Mar 2015; Ian Delaney <idella4@gentoo.org> +roccat-tools-3.1.0.ebuild, -roccat-tools-2.0.0.ebuild, -roccat-tools-2.1.0.ebuild, -roccat-tools-2.2.0.ebuild, metadata.xml: bump; rm old, fixes bug #541590 closing. Once you understand stable in gentoo you're free to make a bug requesting stabling of roccat-tools-2.4.0.
