From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49816) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gCs18-0006As-J3 for guix-patches@gnu.org; Wed, 17 Oct 2018 16:02:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gCs14-0000WP-3Z for guix-patches@gnu.org; Wed, 17 Oct 2018 16:02:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:51435) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gCs13-0000VX-U4 for guix-patches@gnu.org; Wed, 17 Oct 2018 16:02:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gCs13-0005sV-P6 for guix-patches@gnu.org; Wed, 17 Oct 2018 16:02:01 -0400 Subject: [bug#33026] [PATCH] gnu: Add pdns. Resent-Message-ID: References: <20181012185854.9873-1-me@tobias.gr> <8736t7c6rv.fsf@gnu.org> From: Tobias Geerinckx-Rice In-reply-to: <8736t7c6rv.fsf@gnu.org> Date: Wed, 17 Oct 2018 22:01:11 +0200 Message-ID: <875zy0bawo.fsf@tobias.gr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 33026@debbugs.gnu.org Ludo', Ludovic Court=C3=A8s wrote: > What about =E2=80=9Cpowerdns=E2=80=9D then? This patch originally added 'powerdns' (my preference), then I=20 changed it :-) pdns is the far more common name in GNU/Linux land. The BSDs tend=20 to go with powerdns. - pdns: Alpine, Debian, Fedora, Gentoo, brew, openSUSE, Slackware=20 :-), 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=20 the review. POLA and all that. > Why not keep all the commands in the same output? Is it to=20 > avoiding > cluttering user profiles, or is it a matter of package size? The former. Building them is not the upstream default, and I=20 personally don't like them littering my profile (this is entirely=20 subjective). On the other hand I don't think users should have to go so far as=20 to customise the package to get to the tools, so this was the=20 compromise. I don't think either is ideal. >> +Domain Name System (@dfn{DNS}) that supports a wide variety of=20 >> storage methods. > > I think you can avoid @dfn here as well. :-) OK. I'll also remove it from my (already reviewed) NSD package for=20 consistency. > A few questions: > > =E2=80=A2 Are things under ext/ simply bundled libraries? If so, do=20 > you think > there=E2=80=99s something we could/should do about them? I'll take a closer look. > =E2=80=A2 I suppose we don=E2=80=99t build and thus don=E2=80=99t care = about the=20 > license of > modules/oraclebackend, do we? :-) Hm, is that how this works? Or is Oracle's DB non-free? I know=20 nothing about Oracle, which might itself be the anwser to that=20 question. If it is, shouldn't we remove the whole thing in a snippet unless=20 the build system really hates that? > =E2=80=A2 The license of m4/* doesn=E2=80=99t matter for the combined w= ork;=20 > I=E2=80=99d just > remove it. OK. I'll never fully grasp these legal combinatorics. > =E2=80=A2 GPLv2-only code cannot be combined with GPLv3+ code. Is it=20 > really > what=E2=80=99s happening? Let's hope and assume not, then. Closer look. Thanks! T G-R