Date: Sat, 13 Mar 2021 15:48:53 -0800 From: Kevin Oberman <rkoberman@gmail.com> To: "Dan Mahoney (Ports)" <freebsd@gushi.org> Cc: Guido Falsi <mad@madpilot.net>, "Hartmann, O." <ohartmann@walstatt.org>, FreeBSD Ports <freebsd-ports@freebsd.org>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: On 14-CURRENT: no ports options anymore? Message-ID: <CAN6yY1uPRi00ErNVf9zNhJsgAgND_7%2BP3-=WSWieOhToV6z4-A@mail.gmail.com> In-Reply-To: <3779241B-6501-45A5-A63C-7A10DC9FDBF0@gushi.org> References: <20210313201702.5f9dfa9b@hermann.fritz.box> <8a39cc8f-df2b-8a43-54c4-44eebb4b12de@madpilot.net> <3779241B-6501-45A5-A63C-7A10DC9FDBF0@gushi.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 13, 2021 at 2:51 PM Dan Mahoney (Ports) <freebsd@gushi.org> wrote: > If this isn=E2=80=99t at least in /usr/ports/UPDATING it sure should be. > > -Dan > Ditto! While it did not take me long to discover that the ncurses shareable had bumped the version, I wasted a lot of time rebuilding ports one by one. At least a heads-up would have been nice. The way to do this is unclear, though, as it was a base library update. I assume that it only bit those running current or 13. Those running 13-STABLE, as I was, had no warning. I'm not sure a note in UPDATING would have been appropriate, but a post to stable@ and current@ would have been nice. Or, did I miss them? This would also be made VERY clear in the 13.0 Release Notes. I suspect installing misc/compat12x would have worked. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1uPRi00ErNVf9zNhJsgAgND_7%2BP3-=WSWieOhToV6z4-A>