Disable selfupdate (or has this been done already somewhere?)

[barracuda156]

@RJVB [This is not a bug, but rather a request for help on the issue.] How do you solve this in macstrop? I keep getting reports that someone ran selfupdate and screwed up – unsurprisingly – the base, since the code is pulled from the mainstream source, and apparently the rebuild is done with default settings, which is something nearly guaranteed to be breaking. Sure enough, nobody pays attention to notes or instructions, so while I have mentioned on multiple occasions to avoid using that command completely, the issue keeps resurfacing.
I am asking, since there may be an existing solution, and I do not have to re-invent a bicycle. If there is none, I will find a way to deal with this on my fork’s side.

[RJVB]

On Friday August 22 2025 11:26:00 Sergey Fedorov wrote: @RJVB [This is not a bug, but rather a request for help on the issue.] How do you solve this in macstrop?

I don't... I'm not certain what you mean with

since the code is pulled from the mainstream source, and apparently the rebuild is done with default settings

I haven't run `selfupdate` for ages so I can't remember if it also upgrades "base" or only the ports trees followed by an upgrade of all outdated ports. The latter shouldn't cause issues (or else something must be done to set the default compiler!), and it should be trivial to disable any updating of "base" itself ... if you're pushing users to use a customised "base" already.

[barracuda156]

It messes up with the base, and the issue is not specific to my fork. See, for example: https://forums.macrumors.com/threads/whats-the-current-state-of-macports-on-tiger.2417693/?post=34074662#post-34074662

I never use it myself – I did try it once recently, when debugging a weird bug for someone else, and it screwed up the installation LOL