From owner-freebsd-ports@freebsd.org Tue May 30 14:00:21 2017 Return-Path: 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 72F51B7DA6C for ; Tue, 30 May 2017 14:00:21 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from apnoea.adamw.org (apnoea.adamw.org [104.225.5.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "apnoea.adamw.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49CE13076 for ; Tue, 30 May 2017 14:00:20 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id 4e5ab464 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Tue, 30 May 2017 08:00:13 -0600 (MDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: The future of portmaster From: Adam Weinberger In-Reply-To: <201705301351.v4UDpHwY048949@mech-as222.men.bris.ac.uk> Date: Tue, 30 May 2017 08:00:11 -0600 Cc: freebsd-ports@freebsd.org, rollingbits@gmail.com Content-Transfer-Encoding: quoted-printable Message-Id: <9FEDBFCE-27D1-432B-926B-7BF401AD7B19@adamw.org> References: <201705301351.v4UDpHwY048949@mech-as222.men.bris.ac.uk> To: mexas@bris.ac.uk X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 14:00:21 -0000 > On 30 May, 2017, at 7:51, Anton Shterenlikht wrote: >=20 >> when portmaster have gone away? >=20 > What? WHAT? >=20 > portmaster going away??? >=20 > I hope not >=20 > Anton The ports tree continues to evolve. Major new features are planned and = in the process of being implemented. These changes will break all the = port-building tools. poudriere and synth are actively developed, so they will quickly support = the new changes. portmaster and portupgrade are no longer being actively = developed, so it is anticipated that they will stop working until = somebody fixes them (if at all). So no, portmaster isn't going away. But, there's no guarantee that it = will keep working. We strongly, strongly advise everyone to use = poudriere or synth to build their ports, and then plain old "pkg = upgrade" to handle updates. The vast majority of problems reported on this mailing list exist only = in portmaster/portupgrade, because they do not do clean builds. At this = point, portmaster should only be used by people with enough ports = development experience to understand and mitigate conflicts and various = build errors. # Adam --=20 Adam Weinberger adamw@adamw.org https://www.adamw.org