Search Criteria
Package Details: android-udev-git 20200613.r0.ge5bc06e-1
Git Clone URL: | https://aur.archlinux.org/android-udev-git.git (read-only, click to copy) |
---|---|
Package Base: | android-udev-git |
Description: | Udev rules to connect Android devices to your linux box |
Upstream URL: | https://github.com/M0Rf30/android-udev-rules |
Licenses: | |
Conflicts: | |
Provides: | |
Submitter: | robertfoster |
Maintainer: | robertfoster |
Last Packager: | robertfoster |
Votes: | 614 |
Popularity: | 0.005079 |
First Submitted: | 2014-04-26 15:11 |
Last Updated: | 2020-06-13 10:34 |
Dependencies (3)
- libmtp (libmtp-git)
- systemd (systemd-light, systemd-cdown-git, systemd-git, systemd-selinux)
- git (git-git) (make)
Required by (19)
- adb-arm64 (requires android-udev)
- adb-sync-git (requires android-udev)
- android-sdk (requires android-udev) (optional)
- android-sdk-25.2.5 (requires android-udev) (optional)
- android-sdk-cmdline-tools-latest (requires android-udev) (optional)
- android-sdk-cmdline-tools-latest-dummy (requires android-udev) (optional)
- android-sdk-dummy (requires android-udev) (optional)
- droidbot-git (requires android-udev)
- heimdall-git (requires android-udev) (optional)
- heimdall-nogui-git (requires android-udev) (optional)
- openauto-git (requires android-udev) (optional)
- sidequest-bin (requires android-udev)
- sidequest-git (requires android-udev)
- simple-droidcam-client (requires android-udev)
- ubports-installer (requires android-udev)
- ubports-installer-git (requires android-udev)
- unity-editor-android (requires android-udev)
- unity-editor-beta-android (requires android-udev)
- unity-editor-lts-android (requires android-udev)
Latest Comments
« First ‹ Previous ... 7 8 9 10 11 12
vnoel commented on 2010-12-08 11:38
But what do you mean?
Asking people doing it by themselves or creating the group for them in the install file?
I would be in favor of the second case, so it is not important if it is complicated or not since it is automatically done and check for cases where the group has already been added.
If it is for the first case, yes, I agree with you, groupadd is simple enough by itself.
By the way, virtualbox seems to do the same as rtkit:
http://repos.archlinux.org/wsvn/community/virtualbox-ose/trunk/virtualbox.install
But they do not use -r for groupadd in order for it to not be a system group.
So, I propose the following install file:
post_install() {
getent group adbusers >> /dev/null || /usr/sbin/groupadd adbusers || return 1
/bin/cat << EOF
===> In order to use adb, you have to be in the 'adbusers' group
===> For that, use: gpasswd -a USERNAME adbusers
EOF
}
post_upgrade() {
post_install
}
post_remove() {
getent group adbusers &>/dev/null && /usr/sbin/groupdel adbusers
}
Anonymous comment on 2010-12-08 11:11
it seems more complicated...
i prefer groupadd -f adbusers because it's the method used for virtualbox and i'm sure it works.
by the way if this method doesn't work we can change it in future
i'll update package soon
vnoel commented on 2010-12-08 10:31
Yes, seems nice to me :)
We can copy what they do in official packages, for example rtkit add a new group in its install file:
http://repos.archlinux.org/wsvn/packages/rtkit/trunk/rtkit.install
Then tell people to add their user to the group.
Anonymous comment on 2010-12-08 09:35
i like adbusers :)
maybe we can add these lines in the .install file:
# Add adbusers group
groupadd -f adbusers
# Add your user to the adbusers group:
# gpasswd -a USERNAME adbusers
vnoel commented on 2010-12-07 12:34
Hi,
As discussed on android-sdk, we could continue here to see what could be used as a group for enabling access to the devices.
For example at work, our machines can be accessed by anyone using ssh and with the current rules in this package anyone could access my phone connected to my machine!
The same way we have group for accessing disks, cdrom, camera or printer, we could have one for accessing adb devices :)
I propose adbusers but maybe this is not the best.