Package Details: crazyflie-udev 0.1-1

Git Clone URL: (read-only, click to copy)
Package Base: crazyflie-udev
Description: udev rules for Crazyflie by bitcraze.
Upstream URL:
Licenses: MIT
Submitter: dbrgn
Maintainer: acxz
Last Packager: acxz
Votes: 0
Popularity: 0.000000
First Submitted: 2018-10-22 18:41 (UTC)
Last Updated: 2022-02-23 01:42 (UTC)

Dependencies (0)

Required by (1)

Sources (1)

Pinned Comments

acxz commented on 2020-08-24 11:50 (UTC)

Development is on Github: Please open issues and PRs there instead of commenting.

Latest Comments

acxz commented on 2020-08-24 11:50 (UTC)

Development is on Github: Please open issues and PRs there instead of commenting.

acxz commented on 2020-08-24 11:45 (UTC) (edited on 2020-08-24 11:49 (UTC) by acxz)

@dbrgn I really like the optdepends idea. In terms of maintainership, I'm planning on moving the development to GitHub using aurpublish this will allow people to submit PRs and make issues relating packages and just provided an easier format for working with PKGBUILDs.

Let's move the discussion over to Github and feel free to make a PR for adding the optdepends entry.

I'd be willing to hand over maintainership back over to you, but only if you use aurpublish so that it is easier for the community to continue working with the package. We could also make a crazyflie-arch github organization similar to how I have created a rocm-arch github organization for AMD's ROCm packages. See Let me know what you think.

dbrgn commented on 2020-08-24 07:22 (UTC) (edited on 2020-08-24 07:25 (UTC) by dbrgn)

leuko is right, I don't see anything about this package that's out of date. Crazyradio udev rules are in a separate package because some people use the crazyradio independently from the crazyflie project.

I wanted to add an "optdepends" entry for crazyradio-udev, but it seems that acxz somehow took over maintainership, so I can't push? It's possible that I orphaned the package a while ago and forgot :) But I'd still be willing to (co-)maintain this.

acxz: I think it would be better to keep udev rules as a separate package, because you don't necessarily need to depend on the python client in order to connect the crazyflie to a computer. Someone might use alternative software for controlling or flashing. Therefore I think it's better if python-cfclient simply depends on this package and adds an optdepends entry for crazyradio-udev.

acxz commented on 2020-08-23 15:07 (UTC)

It might be a mistake, but I want to include the udev rules in the python-cfclient package directly instead of having a separate package.

Would you be willing to add that in the PKGBUILD for python-cfclient? Would really appreciate that. We can delete this package after we do that.

leuko commented on 2020-08-23 14:55 (UTC) (edited on 2020-08-23 14:58 (UTC) by leuko)

could it be a mistake that this package is flagged out-of-date? I tested it, and the udev rules work for Crazyflie. There is also crazyradio-udev for the USB dongle.