| Git Clone URL: | https://aur.archlinux.org/ledger-udev.git (read-only, click to copy) |
|---|---|
| Package Base: | ledger-udev |
| Description: | Udev rules to connect a ledger wallet to your linux box |
| Upstream URL: | https://www.ledgerwallet.com |
| Licenses: | Apache |
| Submitter: | quest |
| Maintainer: | quest |
| Last Packager: | quest |
| Votes: | 23 |
| Popularity: | 0.34 |
| First Submitted: | 2018-07-26 08:07 (UTC) |
| Last Updated: | 2024-03-25 23:31 (UTC) |
« First ‹ Previous 1 2 3 4
Could the rules be packaged locally at build-time instead? it doesn't seem right to load it remotely, as the behavior is less transparent.
Packaging the rule file in the AUR package would also show the diffs in an AUR manager. Either way the AUR package will need a version bump if the rule file changes, so why not be explicit?
I have enhanced the PKGBUILD to automatically update in case the rules get modified upstream:
https://bin.privacytools.io/?df36fb318a83bfee#8T7MQIrFPdPKeoZkwtLGqpNZyO3rbnqu7iU/u6tHGas=
Thank you ;)
Good idea, we now pull the list from their GitHub. It does a little sed magic to set the MODE and the additional udev-acl tag.
Better to source the rules from upstream itself, so no further maintenance of the package is needed. Plus it's a warrant that no device will be missing at any time.
https://github.com/LedgerHQ/udev-rules/blob/master/20-hw1.rules
Pinned Comments
sshaikh commented on 2023-02-22 20:04 (UTC)
Another two points:
Should this be a vcs package? I understand that the source file doesn't change but since it's being downloaded from master, it's not really a reproducible build and will remain at 1-8 even if the source file changes.
I always have to add MODE="0666" to these udev rules in order to actually access the hardware, as per:
https://wiki.archlinux.org/title/udev#Allowing_regular_users_to_use_devices
is there a strategy here that I'm missing that doesn't require this?