Changes between Initial Version and Version 1 of Ticket #54774, comment 14
- Timestamp:
- Oct 13, 2017, 4:43:49 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #54774, comment 14
initial v1 1 1 You will find that, in general, MacPorts ports are very robust. They tend to be well thought out, carefully tested, and in most cases, they only include the final, accepted fix that the upstream authors want. That is why the ports all work so well, in general, almost all 20,000 of them, and often all the way back to MacOSX Tiger. That is amazing. 2 2 3 There is a price for that kind of thoroughness, however. MacPorts is stricter about it's fixes. Quick one-offs are completely frowned upon, for good reason often. The final fixes take longer.3 There is a price for that kind of thoroughness, however. MacPorts is stricter about it's fixes. Quick one-offs are completely frowned upon, generally for good reason. The final fixes take longer. 4 4 5 So if you're breaking new ground, like a n ow OS version, there will be delays like this. If you can, it helps a great deal to understand what a local repository is <https://guide.macports.org/chunked/development.local-repositories.html>, how to make one and use it, and how to do quick `one-off` fixes for yourself like this. Most of these fixes can be found with 5 or at most 10 minutes of Googling, and adding a small patch or an environment variable define to a Portfile is trivial once you do one or two.5 So if you're breaking new ground, like a new OS version, there will be delays like this. If you can, it helps a great deal to understand what a local repository is <https://guide.macports.org/chunked/development.local-repositories.html>, how to make one and use it, and how to do quick `one-off` fixes for yourself like this. Most of these fixes can be found with 5 or at most 10 minutes of Googling, and adding a small patch or an environment variable define to a Portfile is trivial once you do one or two.