Changes between Initial Version and Version 1 of Ticket #64437, comment 6


Ignore:
Timestamp:
Jan 26, 2022, 4:02:10 AM (2 years ago)
Author:
barracuda156
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #64437, comment 6

    initial v1  
    44Thank you. Yes, I agree, that's the case. After you decided not to continue working on 10.6 PPC, I am the only one here to deal with it.
    55
     6
    67> And then the port maintainer will see how it integrates into the existing port structure. If it is too onerous a fix, you might have to spin off your own repo (that is how TigerPorts came to be). If it is not too onerous, it will likely be included by most port maintainers.
    78
    89I will see examples in port files and try to amend my fixes in a way to make them acceptable (so that they are invoked only in case of 10.6 + ppc). I am not sure yet how to specify case of Rosetta, but in the worst case I think it is safe to assume that it will be either 10.6 PPC or 10.6.8 Rosetta (and nothing in between), and then "OS minor" can be used to trigger Rosetta-specific fixes.
     10
    911
    1012> Some will not accept such a fix no matter what, however, as that adds to the maintenance burden and is of value to very very few people.
     
    1315(In fact I was asked in that thread on Macrumors to write a tutorial how to make Macports work on 10.6 PPC and 10.6.8 Rosetta – essentially that would mean collect your guidelines, simplify them and add Xcode installation steps. I could do that, provided you don't object.)
    1416
     17
    1518> But alternatively, ports that do build as ppc on 10.6 but not on 10.5 might shed some light on how to fix 10.5, and most port maintainers are supportive still.
    1619