Date: Fri, 10 Nov 2023 16:23:27 +0400 From: Vladimir Marchenko <vm.on.tablet2@gmail.com> To: freebsd-ports@freebsd.org Subject: Request to Reconsider the Removal of djbdns from FreeBSD Ports (Regarding Bug 256450) Message-ID: <CAGeVAXyUzmq5CE-yyVQ0Lx4ys%2B6Ca_3uF%2Bn7Q6QU=Wkp2%2BXLXg@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
--000000000000d943080609cb63c1 Content-Type: text/plain; charset="UTF-8" Dear FreeBSD Ports Community, I am a longtime FreeBSD user, having started back in the late 1990s. Yay, it has been since the last century! I am reaching out to request a reconsideration of the decision to remove djbdns from FreeBSD Ports Collection, as discussed in Bug 256450. The decision to deprecate djbdns was primarily based on its status as "unmaintained" and the precedent set by some linux distributions removing it. However, as David Thiel pointed out, tinydns within djbdns is still solid and widely used, and its removal is already causing frustration among users. This indicates a significant user base that still finds value in djbdns. Furthermore, Leo Vandewoestijne raised an important point about the relevance of djbdns, particularly its tinydns-data component, which is still useful and can be integrated with other modern tools like PowerDNS and dnsdist. This underscores the ongoing utility and adaptability of djbdns in contemporary environments. I, personally, found out about this unfortunate "bug resolution" when I once again tried to install dgbdns as a nifty shortcut to have daemontools correctly and easily installed and activated on my system. Daemontools port does not do it by itself. This is just one example. But djbdns is also valuable as a simple and dependable DNS server for local networks where not being an "over engineered monstrosity" is more valuable than strict compliance with all the latest trends and standards. There are NO good reasons to destroy the value gjbdns brings to users of FreeBSD or to destroy value that numerous tips and manuals online involving djbdns bring to FreeBSD users. Also, philosophically, destroying good software in this fashion is what Linux crowd often does for a variety of petty reasons and what FreeBSD simply does not. FreeBSD is indeed valued for being stable, dependable, reliable and to a large degree backward compatible. Let's not ruin that! Somehow, very reasonable objections voiced by Leo Vandewoestijne and David Thiel were summarily ignored and the decision maker in this matter has chosen to rely instead on an obvious logical fallacy "appeal to the [linux] crowd" plus some misguided notions regarding supposed obsolescence and lack of use of djbdns. Additionally, Daniel Engberg somehow assigned the status of bug 256450 as "affects only me" which clearly cannot be further from the truth. Alternatively, if the presence of djbdns port indeed somehow affects only Daniel Engberg, then ruining thousands of setups and workflows of many users just to fix something that affects only Daniel Engberg appears to be all the more nonsensical. Given these discussions and facts, I urge the community and Daniel Engberg personally to reconsider the removal of djbdns. Its continued usage and the integration with other tools demonstrate its enduring relevance. Let's continue to support the diverse needs of our user base by retaining this valuable software. Thank you for considering this request. I look forward to our community's continued commitment to supporting a wide range of software needs while ensuring FreeBSD remains reliable, dependable and backward compatible as much as possible. Best wishes, Vladimir Marchenko. --000000000000d943080609cb63c1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"> <div><p>Dear FreeBSD Ports Community,</p><p>I am a longtime FreeBSD=20 user, having started back in the late 1990s. Yay, it has been since the=20 last century! I am reaching out to request a reconsideration of the=20 decision to remove djbdns from FreeBSD Ports Collection, as discussed in Bu= g 256450.</p> <p> </p>The decision to deprecate djbdns was primarily based on its status as= =20 "unmaintained" and the precedent set by some linux distributions = removing it. However, as David Thiel pointed out, tinydns within djbdns is still=20 solid and widely used, and its removal is already causing frustration among= =20 users. This indicates a significant user base that still finds value in djb= dns. <br><p>Furthermore, Leo Vandewoestijne raised an important point about the relevance of=20 djbdns, particularly its tinydns-data component, which is still useful=20 and can be integrated with other modern tools like PowerDNS and dnsdist. This underscores the ongoing utility and adaptability of djbdns in=20 contemporary environments.</p></div>I, personally, found out about this=20 unfortunate "bug resolution" when I once again tried to install d= gbdns=20 as a nifty shortcut to have daemontools correctly and easily installed and = activated=C2=A0=20 on my system. Daemontools port does not do it by itself. This is just one= =20 example. But djbdns is also valuable as a simple and dependable DNS server = for local networks where not being an "over engineered monstrosity&quo= t; is more valuable than strict compliance with all the latest trends and s= tandards.<br><br>There are NO good reasons to destroy the value gjbdns brin= gs to users of FreeBSD or to destroy value that numerous tips and manuals=20 online involving djbdns bring to FreeBSD users.<br><p> </p> Also,=20 philosophically,=20 destroying good software in this fashion is what Linux crowd=20 often does for a variety of petty reasons and what FreeBSD simply does not.= FreeBSD is indeed valued for=20 being stable, dependable, reliable and to a large degree backward=20 compatible. Let's not ruin that!<div> <p> Somehow, very reasonable objections voiced by=20 Leo Vandewoestijne and=20 David Thiel were summarily ignored and the decision maker in this matter has chosen to rely instead on an obvious logical fallacy "appeal to t= he [linux] crowd" plus some misguided notions regarding supposed obsoles= cence and lack of use of djbdns.<br></p><p>Additionally,=20 <span class=3D"gmail-vcard"><span class=3D"gmail-fn">Daniel Engberg somehow= </span></span>assigned the status of bug=20 256450 as "affects only me" which clearly cannot be further from = the truth. Alternatively, if the presence of djbdns port indeed somehow aff= ects only=20 <span class=3D"gmail-vcard"><span class=3D"gmail-fn">Daniel Engberg</span><= /span>, then ruining thousands of setups and workflows of many users just t= o fix something that affects only=20 <span class=3D"gmail-vcard"><span class=3D"gmail-fn">Daniel Engberg</span><= /span> appears to be all the more nonsensical.<br><br>Given these discussions and facts, I urge the community and=C2=A0 <span class=3D"gmail-vcard"><span class=3D"gmail-fn">Daniel Engberg</span><= /span> personally to reconsider the removal of=20 djbdns. Its continued usage and the integration with other tools=20 demonstrate its enduring relevance. Let's continue to support the=20 diverse needs of our user base by retaining this valuable software.</p><p>T= hank you for considering this request. I look forward to our community's=20 continued commitment to supporting a wide range of software needs while=20 ensuring FreeBSD remains reliable, dependable and backward compatible as much as possible.</p><p>Best wishes,</p>Vladimir Marchenko.<div class=3D"g= mail-yj6qo"></div><div class=3D"gmail-adL"><br></div></div> </div> --000000000000d943080609cb63c1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGeVAXyUzmq5CE-yyVQ0Lx4ys%2B6Ca_3uF%2Bn7Q6QU=Wkp2%2BXLXg>