[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] gnu: whois: Move mkpasswd to its own output.

From: ng0
Subject: Re: [PATCH] gnu: whois: Move mkpasswd to its own output.
Date: Sat, 21 Jan 2017 00:45:14 +0000

Ludovic Courtès <address@hidden> writes:

> ng0 <address@hidden> skribis:
>> Ludovic Courtès <address@hidden> writes:
>>> Hey,
>>> ng0 <address@hidden> 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’.
>> And upstreams decision is not to do it (on making it a choice not
>> to build it or to move it to another tarball):
>> "No, but thank you for asking."
> So upstream’s decision is to keep mkpasswd in whois?
>> So we stick with the default case? I'm still in favor for making
>> it separate guix packages.
> I’m still in favor of sticking to upstream’s decision, whatever that
> is.  But honestly, I fail to see why this is a big deal.  :-)
> Thanks,
> Ludo’.

Okay. If someone comes up with it again, we can discuss it. For
me it is done.
♥Ⓐ  ng0 --

reply via email to

[Prev in Thread] Current Thread [Next in Thread]