For the record, you can always stop a build by typing CTRL-C, and it will not corrupt anything. Only at the install stage are any files permanently changed. If you do "port clean" after stopping the build, you will be right back where you were before the build.
David On Tue, Mar 20, 2018 at 4:13 PM, Riccardo Mottola via macports-users < macports-users@lists.macports.org> wrote: > Hi, > > Chris Jones wrote: > >> IMHO we shouldn't do anything to support Mac OS versions that aren't >>> getting security patches from Apple anymore (since it's a dis-service to >>> the rest of the people who use the internet when we make it easier for >>> people to keep unpatched machines connected to that shared resource). >>> >> Glad someone else has the same view on this as me. Completely agree. >> >> > > Personally, I disagree... it may be because I usem and because any of the > mac I have can get updates, even if the hardware is fine and perfectly fine > software can run on it. Almost any dual-core intel mac is quite fine for > everyday usage, and running the last available (sadly becoming obsolete) > Firefox versions shows hoe nice those computers are. > > Regarding PPC of course things are a bit worse, but there is "high value" > in those machines because of their architecture (in my opinion "superior" > or in an case "unique") and which is still a nice way to test e.g. > Big-Endianness in a conveninet way or in any case portability. > For others it has some "value", being the last in-house developed boards > of Apple instead of commodity stuff slapped in a cool Apple case. > > I get a tear that I can run more op-to-date software on an old WIndows XP > PC than on a much more modern Mac, with 10.5 or even 10.7. > Just because Apple leaves people in the dust much earlier, free software > shouldn't, even if it does. > > Sorry for the rant... I just love those old Macs too much. I need for them > only one thin.. current TLS and a browser and they would be ready for every > day! > > Riccardo >
