> On 2018-05-30, at 22:20, Ryan Schmidt <ryandes...@macports.org> wrote: > > > On May 30, 2018, at 12:48, macpo...@parvis.nl wrote: > >> $ port livecheck macports >> MacPorts seems to have been updated (port version: 2.5.0, new version: >> 2.5.0-rc1) >> >> missed this one in the release process ? > > Doesn't really matter; nobody but MacPorts release engineers should be doing > anything with the MacPorts port, and I hope to phase it out entirely in the > future. Livecheck is used by developers who want to know if a new version of > software exists upstream; since we are the upstream providers of the MacPorts > software, we already know when new versions are released; we don't need to > use livecheck on this port. We could just turn livecheck off. But for now > I've fixed the livecheck to skip non-stable versions: > > https://github.com/macports/macports-ports/commit/e311180236fe209b3fbb720187c2b15e39c068df
OK. Guess I'll have to learn to ask what I want, not what I think ... I have several macs with a normal MacPorts installation with lots of ports running fine, with daily port selfupdate, port upgrade outdated, and more. For munin I created a second MacPorts environment, without selfupdate etc, because while working on a specific item, I don't want to be disturbed by changes in MacPorts version of changed ports I depend on. But I do want to know when that happens. The other day there it took 2 days to build munin on the other macs and there was not much fun in the differences (like 2.5.0 released, and some subtle changes in ports). As port livecheck works fine for normal ports, and did work fine for port livecheck macports, until 2.5.0, I used that. Q: I'm looking for a [bash] procedure to check if MacPorts has changed *without* doing the selfupdate. Can you make a suggestion? paul.
