all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: "Jelle Licht" <jlicht@fsfe.org>, "Ludovic Courtès" <ludo@gnu.org>
Cc: 27791@debbugs.gnu.org
Subject: [bug#27791] [PATCH] gnu: Add passmenu
Date: Tue, 17 Oct 2017 00:09:56 +0200	[thread overview]
Message-ID: <87efq27nij.fsf@fastmail.com> (raw)
In-Reply-To: <87shejmbml.fsf@fsfe.org>

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

Jelle Licht <jlicht@fsfe.org> writes:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hi Jelle,
>>
>> Is anything holding this back?
>>
>>   https://bugs.gnu.org/27791
>
> It just fell through the cracks, thanks for reminding me :-).
> I still needed to address some of Marius' concerns though...
>
>>
>> TIA!  :-)
>>
>> Ludo’.
>>
>> Marius Bakke <mbakke@fastmail.com> skribis:
>>
>>> Hi Jelle,
>>>
>>> Jelle Licht <jlicht@fsfe.org> writes:
>>>
>>>> Hello guix,
>>>>
>>>> Attached is a patch to include passmenu, a dmenu interface to the pass
>>>> password store.
>>>>
>>>> I was not quite sure how to structure this patch, as it basically installs
>>>> and wraps a shell script from the `password-store' sources. We could
>>>> instead include it as a separate output of our `password-store' package,
>>>> but I already had it like this in my GUIX_PACKAGE_PATH and I was not even
>>>> sure if that approach was in general preferable.
>>>
>>> I don't think wrapping it with dmenu in PATH is necessary. Users of this
>>> script are expected to have dmenu from before, and may want to use
>>> another implementation (e.g. rofi), another version, etc.
>
> While I agree with your general thoughts, wasn't guix supposed to
> prevent this ad-hoc mishmash of software? If someone wants to use
> another implementation (e.g. rofi), they could just create their own
> package that inherits from `password-store' and overrides the "dmenu"
> input. Case in point, I am not currently a user of dmenu (besides
> indirectly through the passmenu script).

In the "rofi" case it would be overriding dmenu and providing some extra
command-line arguments, but overall I agree with you and don't really
have a strong opinion.  To my knowledge there is no established policy
for when to allow "impurities" (aka unqualified paths), but optional
dependencies often get a free pass.

I'm happy either way, so do what you think is best :)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2017-10-16 22:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-22 12:35 [bug#27791] [PATCH] gnu: Add passmenu Jelle Licht
2017-07-22 13:00 ` Marius Bakke
2017-10-16 13:22   ` Ludovic Courtès
2017-10-16 14:05     ` Jelle Licht
2017-10-16 22:09       ` Marius Bakke [this message]
2017-11-10 13:50         ` bug#27791: " Jelle Licht

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=87efq27nij.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=27791@debbugs.gnu.org \
    --cc=jlicht@fsfe.org \
    --cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.