Date: Tue, 30 May 2017 08:00:11 -0600 From: Adam Weinberger <adamw@adamw.org> To: mexas@bris.ac.uk Cc: freebsd-ports@freebsd.org, rollingbits@gmail.com Subject: Re: The future of portmaster Message-ID: <9FEDBFCE-27D1-432B-926B-7BF401AD7B19@adamw.org> In-Reply-To: <201705301351.v4UDpHwY048949@mech-as222.men.bris.ac.uk> References: <201705301351.v4UDpHwY048949@mech-as222.men.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 30 May, 2017, at 7:51, Anton Shterenlikht <mexas@bris.ac.uk> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9FEDBFCE-27D1-432B-926B-7BF401AD7B19>