An entirely open source driver and user-space daemon that allows you to manage your Razer peripherals on GNU/Linux
No description set
-
4
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout hardware:razer/openrazer && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
PKGBUILD | 0000002520 2.46 KB | |
UPDATE.sh | 0000000416 416 Bytes | |
_service | 0000000477 477 Bytes | |
_service:download_url:v2.0.0.tar.gz | 0000166190 162 KB | |
common.sh | 0000000049 49 Bytes | |
copy-from-stable.sh | 0000000186 186 Bytes | |
copy-from-testing.sh | 0000000203 203 Bytes | |
make_debian_dsc.sh | 0000000384 384 Bytes | |
make_debian_orig_tar_gz.sh | 0000000188 188 Bytes | |
make_debian_tar_xz.sh | 0000000937 937 Bytes | |
openrazer-Debian_8.0.dsc | 0000000868 868 Bytes | |
openrazer-Debian_9.0.dsc | 0000000868 868 Bytes | |
openrazer-Debian_Sid.dsc | 0000000868 868 Bytes | |
openrazer.dsc | 0000000870 870 Bytes | |
openrazer.spec | 0000004097 4 KB | |
razer-daemon.install | 0000000194 194 Bytes | |
razer-driver-dkms.install | 0000000603 603 Bytes | |
razer_2.0.0-0.debian.tar.xz | 0000007116 6.95 KB | |
razer_2.0.0.orig.tar.gz | 0000166190 162 KB | |
update_git_commit.sh | 0000000564 564 Bytes | |
update_release.sh | 0000001272 1.24 KB |
Revision 30 (latest revision is 79)
Luca Weiss (z3ntu)
committed
(revision 30)
2.0.0
Comments 2
Did you try to get this into Factory / Tumbleweed? if not I would like to co-maintain if included in Factory.
No I didn't. I kind of prefer maintaining the packages myself as there are no problems with outdated packages being kept in "stable" releases and users having problems with those. And I have this OBS repo anyways for all the other distros where the packages aren't included. I think it would just double the maintenance cost, the package in Factory / Tumbleweed and the one in this repo. And unfortunately openrazer isn't plug&play either, it requires the dkms package to build correct (and people always forget the kernel headers) and the user to be added to the plugdev group, otherwise it won't work correctly.