I'm very interested. I have a Portfile I started here for TenFourFox:
https://github.com/kencu/myports/tree/master/www/tenfourfox It builds to a certain point and then hits an error. Forget what it was just now. But it's a good starting point. At present I use Firefox at present on 10.6.8 (Firefox ESR 45.9.0). It works just great on 10.6.8. https://ftp.mozilla.org/pub/firefox/releases/45.9.0esr/ Also available is webkit2-gtk (I have 2.18.0 running) and epiphany. These work well also. Current versions in same repo above. I will put together a PR to update it on MacPorts once a few final systems build it (getting a few systems to build something is easy -- getting them all to build it is harder). Finally, see this: https://sourceforge.net/p/leopard-webkit/wiki/Home/ Ken On 2017-12-11, at 8:29 AM, Ulrich Wienands wrote: > I would be very much interested. I am setting up a new old laptop for Snow > Leo so I can have access to Rosetta; but TFF does not seem to run under > Rosetta (even the G3 built does not work for me). Also I have a bunch of Mac > Pros under 10.8 that I don’t really want to upgrade, so I am losing support > for Firefox there as well. > > Thanks for looking into this. I would offer help if I could, but it is not > realistic for lack of time and for lack of the skills needed. > > Uli > > >> On Dec 11, 2017, at 10:09 AM, Riccardo Mottola via macports-users >> <[email protected]> wrote: >> >> Hi all, >> >> my interest in MacPorts sparked because I am attempting to port TenFourFox >> to intel... there has been already a past effort (v17) of an Intel port of >> it. >> We all know that Firefox dropped anything 10.8 and below, I wonder if there >> any other persons interested in such an effort? For example people who use >> older MacBooks and MacBook Pro's, Mac Minis which may be anywhere between >> 10.4 and 10.7 ? >> From some bug comments on trac, apparently at least one other person is >> interested. >> >> Mostly, the problems are >> - make the "new" code written custom for TTF for PPC work on Intel, that is >> make it endianess independent. Upstream is quite open to this if the patch >> is clean and we strive to maintain a common base >> - make code paths and dependencies currently not used on PPC work on Intel >> >> Some of teh dependencies are already handled by the ports, so past >> experience helps. >> >> E.g. I have issues with libffi and libvpx. >> >> Anyone interested, reply here or contact me. >> >> Riccardo >
