Re: Using macports 2.6.2 on a powerbook G4 1.33GHz and Leopard 10.5.8 ppc

2020-03-14 Thread Riccardo Mottola via macports-users
Ken Cunningham wrote: Your Leopard machine (PPC or intel) is quite well supported, in a non-official-fashion, with MacPorts, as are almost all macOS systems. Bring all your friends! I would say Leopard forever! ALmost the bast MacOS done.

Re: Using macports 2.6.2 on a powerbook G4 1.33GHz and Leopard 10.5.8 ppc

2020-03-11 Thread Jeffrey Walton
On Wed, Mar 11, 2020 at 10:09 PM Ken Cunningham wrote: > > Some MacPorters are totally uninterested in older systems. That's fine, of > course. However, MacPorts has about 10% of the market, and HomeBrew has about > 90%, and if you ask me, one of the main thing that keeps MacPorts alive these

Re: Using macports 2.6.2 on a powerbook G4 1.33GHz and Leopard 10.5.8 ppc

2020-03-11 Thread Ken Cunningham
> I don't know where to start. Maybe someone can me point into the right > direction, and give me some hints, how to apply patches I have operating 10,4, 10.5, and 10.6 systems running hundreds to thousands of ports that I keep humming along. My PPC machines are running right now, and run many

Re: Using macports 2.6.2 on a powerbook G4 1.33GHz and Leopard 10.5.8 ppc

2020-03-11 Thread Ryan Schmidt
On Mar 9, 2020, at 14:47, ggrubb...@web.de wrote: > I'm not sure, if I should simply wait for macports 2.6.3, or whenever the > patches are updated Updates to MacPorts base are infrequent. MacPorts 2.6.3, whenever we get around to releasing that, would contain bug fixes for MacPorts base, but

Re: Using macports 2.6.2 on a powerbook G4 1.33GHz and Leopard 10.5.8 ppc

2020-03-10 Thread Gerhard Gaussling
cports.org Betreff: Re: Using macports 2.6.2 on a powerbook G4 1.33GHz and Leopard 10.5.8 ppc This will fix libgcc7, I believe, but I have to test it formally first: <https://trac.macports.org/ticket/59832#comment:14> I have fixed python38 (twice, sigh), but the current fix looks robust

Re: Using macports 2.6.2 on a powerbook G4 1.33GHz and Leopard 10.5.8 ppc

2020-03-09 Thread Ken Cunningham
This will fix libgcc7, I believe, but I have to test it formally first: I have fixed python38 (twice, sigh), but the current fix looks robust and should make it through once it is properly vetted by the maintainer: