Date: Sun, 7 Feb 2016 17:02:08 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: =?ISO-8859-15?Q?Torsten_Z=FChlsdorff?= <mailinglists@toco-domains.de> Cc: "Greg 'groggy' Lehey" <grog@FreeBSD.org>, ports@freebsd.org Subject: Re: Removing documentation Message-ID: <alpine.BSF.2.20.1602071700150.74300@wonkity.com> In-Reply-To: <56B72E20.80909@toco-domains.de> References: <20160207000304.GA71035@eureka.lemis.com> <56B72E20.80909@toco-domains.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 7 Feb 2016, Torsten Zühlsdorff wrote: > Hello, > >>> You have a tool presented as "official" that hasn't had it's >>> original maintainer in 4 years and was only kept on life support up >>> until 9 months ago. >> >> Agreed, the "official" (the term used is "recommended") status is >> gone. But that's a reason to fix the documentation, not remove it. >> As I see it, we have three choices, in increasing order of >> desirability: >> >> 1. Remove all mention of portmaster. That's what this PR recommends. >> 2. Do nothing. >> 3. Update the documentation to indicate the current status, >> recommending alternatives if possible. > > Number 4 is missing: find a maintainer for it. > > I would volunteer for this. But before a real commitment i need a closer look > at it, which i will do next week. So please standby. Thank you. From owner-freebsd-ports@freebsd.org Mon Feb 8 00:29:55 2016 Return-Path: <owner-freebsd-ports@freebsd.org> Delivered-To: freebsd-ports@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 993E0AA1F1E for <freebsd-ports@mailman.ysv.freebsd.org>; Mon, 8 Feb 2016 00:29:55 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A756795 for <freebsd-ports@freebsd.org>; Mon, 8 Feb 2016 00:29:55 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id u180Ts3m087890 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 7 Feb 2016 17:29:54 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u180TrUK087887; Sun, 7 Feb 2016 17:29:54 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sun, 7 Feb 2016 17:29:53 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: John Marino <freebsdml@marino.st> cc: FreeBSD Mailing List <freebsd-ports@freebsd.org>, Kevin Oberman <rkoberman@gmail.com> Subject: Re: Removing documentation (was: [Bug 206922] Handbook: Chapter 4.5+ changes) In-Reply-To: <56B754A8.3030605@marino.st> Message-ID: <alpine.BSF.2.20.1602071702120.74300@wonkity.com> References: <56B754A8.3030605@marino.st> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 07 Feb 2016 17:29:54 -0700 (MST) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>; List-Post: <mailto:freebsd-ports@freebsd.org> List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 08 Feb 2016 00:29:55 -0000 On Sun, 7 Feb 2016, John Marino wrote: >> I am not portmgr, but do use portmaster for updating ports on systems >> running STABLE or HEAD. I still see no tool which provides the features of >> portmaster. I also realize that this is far from a universal opinion. > > Please do an honest "fly-off" between ports-mgmt/portmaster and > ports-mgmt/synth. I would love to hear what signficant thing portmaster > can do that Synth can't. (honestly) portmaster's one big feature has always been that it has no dependencies. That was and is important. One of the motivators for portmaster was portupgrade's Ruby and ruby-bdb dependencies, which often broke upgrades. I have not tried Synth due to the Ada dependency, and so do not know if it has other portmaster-like abilities, like installing or upgrading a port from the command line with just an origin (portmaster devel/git) or whether it can build or upgrade a port or group of interdependent ports on the host system rather than in a chroot or jail. > That's not the point. The point is a sanctioned "official" tool is not > maintained and my position is that is UNACCEPTABLE. To be in the > handbook it must be a hard requirement to be *ADEQUATELY* maintained. I > do not believe that requirement is being met today. I have committed a change to the Handbook that rewords the portmaster entry. It removes "recommended", replacing it with "smallest", and clarifies and simplifies some other text.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1602071700150.74300>