From nobody Fri Nov 10 12:35:29 2023 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SRdb02gKPz50bSf for ; Fri, 10 Nov 2023 12:35:40 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) Received: from mail.sub.ru (mail.sub.ru [88.212.205.2]) by mx1.freebsd.org (Postfix) with SMTP id 4SRdZz21rwz4K4K for ; Fri, 10 Nov 2023 12:35:37 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of tarkhil@webmail.sub.ru has no SPF policy when checking 88.212.205.2) smtp.mailfrom=tarkhil@webmail.sub.ru; dmarc=none Received: (qmail 58153 invoked from network); 10 Nov 2023 15:35:29 +0300 Received: from 109-252-40-162.nat.spd-mgts.ru (109-252-40-162.nat.spd-mgts.ru [109.252.40.162]) by mail.sub.ru ([88.212.205.2]) with ESMTP via TCP; 31 Dec 1969 23:59:59 -0000 Content-Type: multipart/alternative; boundary="------------UZ8ygmnl41WXfZKL7riHNZN0" Message-ID: <38b84f7f-b502-421d-9969-6fe50025264c@webmail.sub.ru> Date: Fri, 10 Nov 2023 15:35:29 +0300 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Request to Reconsider the Removal of djbdns from FreeBSD Ports (Regarding Bug 256450) To: ports@freebsd.org References: Content-Language: en-US From: =?UTF-8?B?0JDQu9C10LrRgdCw0L3QtNGAINCf0L7QstC+0LvQvtGG0LrQuNC5?= In-Reply-To: X-Spamd-Result: default: False [0.02 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_SPAM_MEDIUM(0.99)[0.988]; NEURAL_HAM_SHORT(-0.98)[-0.975]; RCVD_NO_TLS_LAST(0.10)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; XM_UA_NO_VERSION(0.01)[]; MLMMJ_DEST(0.00)[ports@freebsd.org]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_ONE(0.00)[1]; R_SPF_NA(0.00)[no SPF record]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[sub.ru]; ARC_NA(0.00)[]; ASN(0.00)[asn:39134, ipnet:88.212.192.0/20, country:RU]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4SRdZz21rwz4K4K X-Spamd-Bar: / This is a multi-part message in MIME format. --------------UZ8ygmnl41WXfZKL7riHNZN0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit I can't overexpress how much I agree On 10.11.2023 15:23, Vladimir Marchenko wrote: > > 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. > --------------UZ8ygmnl41WXfZKL7riHNZN0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

I can't overexpress how much I agree

On 10.11.2023 15:23, Vladimir Marchenko wrote:

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.

--------------UZ8ygmnl41WXfZKL7riHNZN0--