Yes, you got it. How do I command MacPorts to upgrade all outdated ports "and not" this whatever troublesome port? Is there a way? If you just told me, you'll have to be less subtle.
> On Sep 12, 2022, at 14:00, Bill Cole > <[email protected]> wrote: > On 2022-09-12 at 12:04:41 UTC-0400 (Mon, 12 Sep 2022 12:04:41 -0400) > <[email protected]> > is rumored to have said: > >> Thanks for catching that. >> >> From my macports.conf file: >> # CPU architecture to target. Supported values are "ppc", "ppc64", >> # "i386", "x86_64", and "arm64". Defaults to: >> # - Mac OS X 10.5 and earlier: "ppc" on PowerPC, otherwise "i386". >> # - Mac OS X 10.6 - 10.15: "x86_64" on 64-bit Intel, otherwise "i386". >> # - macOS 11 and later: "arm64" on Apple Silicon, otherwise "x86_64". >> build_arch x86_64 >> >> >> thus, I was not trying to build for i386, I've specified x86_64 > > If for some reason you had built it with the 'universal' variant you could > also end up rebuilding it for both. But as I said, I don't think this is the > point of attack. > >> I find it difficult to believe MacPorts has no control over what it is >> updating. >> MacPorts upgrade command obviously has some way to know what ports have >> updates available: >> >> port upgrade outdated >> >> The outdated argument tells upgrade what to update. I was hoping it would be >> something simple like >> >> port upgrade outdated -libgcc9 > > Like I said... > > >>> On Sep 12, 2022, at 09:29, Bill Cole >>> <[email protected]> wrote: > [...] > >>> 3. "sudo port upgrade outdated and not libgcc9" should work, but it will >>> leave everything dependent on libgcc9 at older versions. > > The only difference from your hypothetical command is 'and not' instead of '-' > > > -- > Bill Cole > [email protected] or [email protected] > (AKA @grumpybozo and many *@billmail.scconsult.com addresses) > Not Currently Available For Hire
