Here‘s an in depth discussion on SSD reliability, a little more detailed than
„(not) recommended“ from someone with a lot of first hand experience, it seems:
https://www.backblaze.com/blog/how-reliable-are-ssds/
Same here: installing XCode and opening it once seems to install command line
tools. At least they are listed in Preferences as installed (at the same path
as XCode.app).
Seems as if no separate install is required with 12.x anymore.
> Am 16.11.2020 um 06:41 schrieb Wahlstedt Jyrki :
>
>
>
You could probably check out the port tree from 2018 into a local folder and
use that in sources.conf as the only entry.
> Am 20.08.2020 um 18:34 schrieb Wowfunhappy :
>
> Hello!
>
> I'm running Mavericks, because I want to and it's my favorite OS.
> Sometimes—understandably—things break on
You may want to ask Avast this question.
FWIW: the link works for me (FireFox on macOS) and logs me into Trac via Github
as expected.
> If you change a setting in macports.conf, you should uninstall and reinstall
> any ports affected by that setting.
Ryan, thank a lot for the explanations and the guide to selectively reinstall!
Worked like a charm and after using MP for years I now actually experience how
much faster
> If you think about it for a moment you will realize there is no way to use
> the prebuilt binaries with non-standard installation options.
Application bundles are supposed to be self contained and movable, afaik, and I
would expect those built by macports to be that, too.
> From
>
> The prebuilt ports on the buildbot are not building their ports to go into
> /Applications, so therefore they don’t match your setup — so you can’t use
> them (even though many would be OK, it’s an all-or-nothing thing.
Ok, so what if I want to change back to the default and set
> One thing that I've learned (thanks to people like Ryan and you etc) is to
> *never* touch MacPorts unless you are aware of the consequences. It's not
> that it's fragile -- far from it -- it's just that there are few
> user-serviceable parts inside.
Well, thats the point: the conf files
So I was wondering why it seems "port install" is always end up building from
source on my machine and came across this in archive_sites.conf:
> # prefix: The prefix of the MacPorts installation used to create the
> # source's archives. This must match the value of "prefix" set in
> #
