From owner-freebsd-doc@freebsd.org Fri Feb 5 14:59:19 2016 Return-Path: Delivered-To: freebsd-doc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88361A9A9CD for ; Fri, 5 Feb 2016 14:59:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 611C39AD for ; Fri, 5 Feb 2016 14:59:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u15ExJwF038517 for ; Fri, 5 Feb 2016 14:59:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-doc@FreeBSD.org Subject: [Bug 206922] Handbook: Chapter 4.5+ changes Date: Fri, 05 Feb 2016 14:59:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Documentation X-Bugzilla-Component: Documentation X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marino@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-doc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2016 14:59:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206922 --- Comment #4 from John Marino --- (In reply to Warren Block from comment #3) "At present, portmaster still has no direct competition. It is a no-dependencies shell script. portupgrade is the closest thing, but Ruby a= nd ruby-bdb dependencies cause trouble on upgrades." 1) I disagree about the competition 2) it's irrelevant. You can't recommend it officially and not have it maintained, period. "As far as maintenance, nobody wants to maintain dense shell script. (The reasons for portmaster being in sh are debatable in their own right, but not relevant to this discussion.)" Au contraire, it's the heart of the discussion. No maintainer, get it out = of the documentation ASAP. "Until there is a close replacement, or portmaster is no longer functional, removing it from the documentation is premature. That is not a statement on the desirability of the situation, just an instance of BSD pragmatism." It has a man page, it doesn't need to be in the freebsd handbook. ################################################ There is a serious catch-22 going on. The portmgr doesn't want to deprecate it as long as it is in documentation,= and the docs guys don't want to remove it as long as it is in ports.=20=20 Both desires cannot exist. you do NOT want new users of portmaster in this state. You are not doing t= hem any service as all. Why is the concept even a discussion? How can you RECOMMEND non-maintained buggy software in the official handbook? Whether or not it has competition= is irrelevant. --=20 You are receiving this mail because: You are the assignee for the bug.=