Github messages for voidlinux
 help / color / mirror / Atom feed
From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: android-file-transfer-linux: depend on libmtp-udev (newly split)
Date: Wed, 17 Jan 2024 00:55:07 +0100	[thread overview]
Message-ID: <20240116235507.171C028E7C@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47378@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 460 bytes --]

New comment by dkwo on void-packages repository

https://github.com/void-linux/void-packages/pull/47378#issuecomment-1894704509

Comment:
libmtp also ships some udev rules that are useful to other packages using MTP, e.g. android-file-transfer.
we split those in a subpackage, and make aft depend on it.
without this, one cannot use e.g. aft-mtp-mount (not even after installing android-udev-rules).
with this, it is enough to be a member of plugdev group.

  parent reply	other threads:[~2024-01-16 23:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24 21:57 [PR PATCH] android-file-transfer-linux: add libmtp to depends dkwo
2023-11-25 16:37 ` biopsin
2023-12-12 20:12 ` [PR PATCH] [Closed]: " dkwo
2023-12-12 20:12 ` dkwo
2023-12-12 21:15 ` dkwo
2023-12-12 21:15 ` [PR PATCH] [Updated] " dkwo
2023-12-12 21:25 ` dkwo
2023-12-13 17:15 ` dkwo
2023-12-14 15:43 ` dkwo
2023-12-14 15:44 ` dkwo
2023-12-14 15:44 ` dkwo
2023-12-23 19:07 ` [PR PATCH] [Updated] android-file-transfer-linux: depend on libmtp-udev (newly split) dkwo
2023-12-24  8:30 ` dkwo
2023-12-24 20:15 ` dkwo
2023-12-26 18:00 ` dkwo
2023-12-27 16:22 ` dkwo
2024-01-16 22:46 ` dkwo
2024-01-16 23:33 ` tornaria
2024-01-16 23:55 ` dkwo [this message]
2024-01-17  0:31 ` tornaria
2024-01-31 21:20 ` dkwo
2024-02-01  0:36 ` Duncaen
2024-02-01  0:37 ` Duncaen
2024-02-01 16:03 ` [PR PATCH] [Closed]: " dkwo
2024-02-01 16:03 ` dkwo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240116235507.171C028E7C@inbox.vuxu.org \
    --to=dkwo@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).