From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Regarding packages pass, pass-otp, passmenu. Clipboard terminal program required. Passmenu requires GUI pinentry-program
Date: Wed, 15 Jan 2025 20:05:23 +0100 [thread overview]
Message-ID: <20250115190523.9BC6D20250@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53870@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/53870#issuecomment-2593729622
Comment:
I regularly use `pass`, and most of the use isn't copying things to a clipboard. The application doesn't do "nothing" without a clipboard program. Furthermore, the program's use of these tools is listed right in the [manual page](https://man.voidlinux.org/pass).
The lack of optional dependencies in XBPS is neither a bug nor a feature, but a *limitation*. The fact that we don't thrust unnecessary sets of dependencies on all users just to placate an arbitrary subset of them most definitely *is* a feature.
You know what tools you were missing and have solved your problem. It's time to move on to more important things!
next prev parent reply other threads:[~2025-01-15 19:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 20:03 [ISSUE] " computative
2025-01-06 20:20 ` classabbyamp
2025-01-07 8:08 ` computative
2025-01-07 8:09 ` computative
2025-01-07 8:10 ` computative
2025-01-07 8:10 ` computative
2025-01-07 8:10 ` computative
2025-01-07 8:12 ` computative
2025-01-07 8:19 ` computative
2025-01-07 8:19 ` computative
2025-01-12 17:39 ` ahesford
2025-01-12 17:39 ` [ISSUE] [CLOSED] " ahesford
2025-01-15 18:10 ` computative
2025-01-15 19:05 ` ahesford [this message]
2025-01-15 23:46 ` computative
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=20250115190523.9BC6D20250@inbox.vuxu.org \
--to=ahesford@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).