You mention release notes. Slightly off-topic, but I never understood why, if there was a beta or RC available, the release-notes of the time weren’t available on www.freebsd.org <http://www.freebsd.org/>. Wouldn’t that make sense to see if there were things you wanted to try out and test? Anyway, more on topic, it seems that if one is on -CURRENT (or possibly -STABLE), you’re building from source, and should be expected to read UPDATING. That much is on the site. (But that would be /usr/src, not /usr/ports). Did this happen mid-line in a stable? That…shouldn’t. -Dan > On Mar 13, 2021, at 3:48 PM, Kevin Oberman <rkoberman_at_gmail.com> wrote: > > On Sat, Mar 13, 2021 at 2:51 PM Dan Mahoney (Ports) <freebsd_at_gushi.org> > wrote: > >> If this isn’t 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_at_ and current_at_ 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_at_gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > _______________________________________________ > freebsd-ports_at_freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe_at_freebsd.org"Received on Sat Mar 13 2021 - 23:29:49 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:27 UTC