From: Tobias Geerinckx-Rice <me@tobias.gr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 33026@debbugs.gnu.org
Subject: [bug#33026] [PATCH] gnu: Add pdns.
Date: Wed, 17 Oct 2018 22:01:11 +0200 [thread overview]
Message-ID: <875zy0bawo.fsf@tobias.gr> (raw)
In-Reply-To: <8736t7c6rv.fsf@gnu.org>
Ludo',
Ludovic Courtès wrote:
> What about “powerdns” then?
This patch originally added 'powerdns' (my preference), then I
changed it :-)
pdns is the far more common name in GNU/Linux land. The BSDs tend
to go with powerdns.
- pdns: Alpine, Debian, Fedora, Gentoo, brew, openSUSE, Slackware
:-), and derivatives
- power: Arch, *BSD, Nix :-), and derivatives
The upstream tarball also uses the pdns- prefix.
So I'm all for using 'power' but expected some astonishment during
the review. POLA and all that.
> Why not keep all the commands in the same output? Is it to
> avoiding
> cluttering user profiles, or is it a matter of package size?
The former. Building them is not the upstream default, and I
personally don't like them littering my profile (this is entirely
subjective).
On the other hand I don't think users should have to go so far as
to customise the package to get to the tools, so this was the
compromise.
I don't think either is ideal.
>> +Domain Name System (@dfn{DNS}) that supports a wide variety of
>> storage methods.
>
> I think you can avoid @dfn here as well. :-)
OK. I'll also remove it from my (already reviewed) NSD package for
consistency.
> A few questions:
>
> • Are things under ext/ simply bundled libraries? If so, do
> you think
> there’s something we could/should do about them?
I'll take a closer look.
> • I suppose we don’t build and thus don’t care about the
> license of
> modules/oraclebackend, do we? :-)
Hm, is that how this works? Or is Oracle's DB non-free? I know
nothing about Oracle, which might itself be the anwser to that
question.
If it is, shouldn't we remove the whole thing in a snippet unless
the build system really hates that?
> • The license of m4/* doesn’t matter for the combined work;
> I’d just
> remove it.
OK. I'll never fully grasp these legal combinatorics.
> • GPLv2-only code cannot be combined with GPLv3+ code. Is it
> really
> what’s happening?
Let's hope and assume not, then. Closer look.
Thanks!
T G-R
next prev parent reply other threads:[~2018-10-17 20:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 18:58 [bug#33026] [PATCH] gnu: Add pdns Tobias Geerinckx-Rice
2018-10-15 20:08 ` Ludovic Courtès
2018-10-17 20:01 ` Tobias Geerinckx-Rice [this message]
2018-10-19 8:35 ` Ludovic Courtès
2019-03-04 16:19 ` [bug#33026] [PATCH v2 0/2] " Tobias Geerinckx-Rice
2019-03-04 16:19 ` [bug#33026] [PATCH v2 1/2] gnu: Add yahttp Tobias Geerinckx-Rice
2019-03-04 16:19 ` [bug#33026] [PATCH v2 2/2] gnu: Add pdns Tobias Geerinckx-Rice
2018-11-07 21:11 ` [bug#33026] [PATCH] " Leo Famulari
2019-02-19 23:07 ` [bug#33026] Progress Andreas Enge
2019-03-07 13:22 ` bug#33026: [bug#33020] Progress Andreas Enge
[not found] ` <87tvge7qjv.fsf@nckx>
2019-03-07 14:02 ` [bug#33026] " Andreas Enge
2019-03-07 14:08 ` Andreas Enge
2019-03-07 14:58 ` Tobias Geerinckx-Rice
-- strict thread matches above, loose matches on Subject: below --
2018-10-11 23:06 [bug#33020] [PATCH] gnu: Add nullmailer Tobias Geerinckx-Rice
2018-10-15 20:01 ` Ludovic Courtès
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=875zy0bawo.fsf@tobias.gr \
--to=me@tobias.gr \
--cc=33026@debbugs.gnu.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 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).