From: ludo@gnu.org (Ludovic Courtès)
To: ng0 <ng0@libertad.pw>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: whois: Move mkpasswd to its own output.
Date: Mon, 09 Jan 2017 15:29:13 +0100 [thread overview]
Message-ID: <87eg0cnw7a.fsf@gnu.org> (raw)
In-Reply-To: <87o9zg7cjb.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (ng0@libertad.pw's message of "Mon, 09 Jan 2017 10:28:24 +0000")
Hey,
ng0 <ng0@libertad.pw> skribis:
> Mkpasswd has nothing to do with whois, and upstream says so. I
> think we should be able to install whois and just have whois, not
> some random "historical bundled" binary in addition to whois.
> I'm just stating the sizes as in comparison to the other outputs
> they sometimes matter even if its just KiB.
>
> Like I've written in the opening email, another approach could be
> to simply delete mkpasswd from the output build and create an
> 'mkpasswd' package (inheriting from whois) which does the same
> for whois.
I might be overlooking something, but my gut reaction is that (1) it’s
not “bundling” in that we don’t have any other package providing
mkpasswd, and (2) it’s up to upstream to decide whether or not to
distribute mkpasswd.
WDYT?
Ludo’.
next prev parent reply other threads:[~2017-01-09 14:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 18:07 "unbundle" mkpasswd from whois ng0
2017-01-04 18:07 ` [PATCH] gnu: whois: Move mkpasswd to its own output ng0
2017-01-09 9:34 ` Ludovic Courtès
2017-01-09 10:28 ` ng0
2017-01-09 14:29 ` Ludovic Courtès [this message]
2017-01-09 14:37 ` ng0
2017-01-09 14:45 ` Whois: Update to 5.2.14 ng0
2017-01-09 14:45 ` [PATCH] gnu: whois: " ng0
2017-01-09 21:05 ` Leo Famulari
2017-01-20 10:41 ` [PATCH] gnu: whois: Move mkpasswd to its own output ng0
2017-01-20 11:32 ` Hartmut Goebel
2017-01-20 13:52 ` Ludovic Courtès
2017-01-21 0:45 ` ng0
2017-01-20 14:02 ` Ricardo Wurmus
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eg0cnw7a.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ng0@libertad.pw \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).