Date: Sat, 13 Mar 2021 16:29:42 -0800 From: "Dan Mahoney (Ports)" <freebsd@gushi.org> To: Kevin Oberman <rkoberman@gmail.com> 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: <1A50C846-307F-4DBE-AECD-2A71547D3C91@gushi.org> In-Reply-To: <CAN6yY1uPRi00ErNVf9zNhJsgAgND_7%2BP3-=WSWieOhToV6z4-A@mail.gmail.com> References: <20210313201702.5f9dfa9b@hermann.fritz.box> <8a39cc8f-df2b-8a43-54c4-44eebb4b12de@madpilot.net> <3779241B-6501-45A5-A63C-7A10DC9FDBF0@gushi.org> <CAN6yY1uPRi00ErNVf9zNhJsgAgND_7%2BP3-=WSWieOhToV6z4-A@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
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@gmail.com> wrote: > > On Sat, Mar 13, 2021 at 2:51 PM Dan Mahoney (Ports) <freebsd@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@ 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 > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1A50C846-307F-4DBE-AECD-2A71547D3C91>