From: ng0 <ng0@n0.is>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 30037@debbugs.gnu.org
Subject: [bug#30037] [PATCH] gnu: whois: Remove bundled mkpasswd.
Date: Wed, 10 Jan 2018 14:55:54 +0000 [thread overview]
Message-ID: <20180110145554.bdnge6atptnrsg7c@abyayala> (raw)
In-Reply-To: <65a6b7e7-afca-cc9e-d1b7-cf23038800d4@tobias.gr>
[-- Attachment #1: Type: text/plain, Size: 1974 bytes --]
Tobias Geerinckx-Rice transcribed 2.6K bytes:
> ng0,
>
> ng0 wrote on 09/01/18 at 07:51:
> > or you could move the mkpasswd to its own output.
>
> That's not (a step towards) unbundling, though, is it?
>
> > I think you want to look into the old discussions around this. I
> > don't remember why this wasn't chosen, all I know is that upstream
> > made it very clear to me that they won't separate mkpasswd.
>
> OK, I found this thread[0] on guix-devel. I'd only checked guix-patches.
>
> I can somewhat understand your use of the word ‘bundle’ in the TODO
> comment — or at least where it came from — but it's pretty misleading in
> that context. As you rightly noted:
>
> Ludo'> Why to you call that “unbundling”?
> ng0> Wrong choice of words.
> [...]
> ng0> It's annoying that two unrelated applications are thrown
> ng0> into one distribution/package.
>
> It would have been nice to adjust the comment at that point, or mention
> that this ‘mkpasswd’ is unrelated to the better-known Expect ‘mkpasswd’.
>
> (Hark, this one doesn't even mk passwds! For maximum irony, it was
> renamed from ‘cryptpw’, which perfectly described its purpose...)
>
> Since this is its own thing, for better or worse, I agree with the
> others in that thread that it should remain part of this package/output
> until upstream repents.
>
> Kind regards,
>
> T G-R
>
> [0]: https://lists.gnu.org/archive/html/guix-devel/2017-01/msg00504.html
>
I had whois installed for some time, but consider this (or test it):
What if someone under account root install 'whois' into their profile.
Wouldn't they have 2 mkpasswd now in their path of exectuables and
encounter a collision?
Should we rename it for the sake of namespace collisions reduction?
--
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
WWW: https://n0.is/a/ :: https://ea.n0.is
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-10 13:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 1:01 [bug#30037] [PATCH] gnu: whois: Remove bundled mkpasswd Tobias Geerinckx-Rice
2018-01-09 1:04 ` Tobias Geerinckx-Rice
2018-01-09 6:51 ` ng0
2018-01-09 16:46 ` Tobias Geerinckx-Rice
2018-01-10 14:55 ` ng0 [this message]
2018-01-10 15:57 ` Tobias Geerinckx-Rice
2018-01-09 13:36 ` Ludovic Courtès
2018-01-09 16:46 ` Tobias Geerinckx-Rice
2018-01-09 17:05 ` Marius Bakke
2018-01-10 14:46 ` ng0
2018-01-10 15:26 ` bug#30037: " Tobias Geerinckx-Rice
2018-01-10 17:17 ` [bug#30037] " ng0
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=20180110145554.bdnge6atptnrsg7c@abyayala \
--to=ng0@n0.is \
--cc=30037@debbugs.gnu.org \
--cc=me@tobias.gr \
/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.