As soon as you change a thing on the system, may it be base OS or may it be ports, you have some kind of a patch.
Now my question is: how do You handle these patches?
Considering that last year we had the 10th anniversary of my bug report (and patch) to the base-OS, PR 122519(*) (which is the reason I don't bother to get an account for the new bug tool), these patches can stay around for quite a while and during multiple releases. SVN does a nice job in merging those things in when upgrading to another release - but nevertheless, they lure around in the source tree, without proper documentation, and tend to get forgotten.
So, one can either live with that, or think about a solution...
(*) and this is not the only one, see e.g. here, or here:
https://stackoverflow.com/questions/53715647/ruby-bundler-fails-with-errnoerofs
https://groups.google.com/forum/#!topic/bareos-users/lAlWhIdXPXk
Probably, these people tend to expect that one becomes a member of their specific developer communities (and adhere to their specific buerocracy), in order to deliver fixes - which then may or may not help the issue. But then, we have some 25'000 ports, and I definitely do not want to become member in dozens of whatever things, just because some coding error decides perchance to hop into my face so that I need to fix it.
Now my question is: how do You handle these patches?
Considering that last year we had the 10th anniversary of my bug report (and patch) to the base-OS, PR 122519(*) (which is the reason I don't bother to get an account for the new bug tool), these patches can stay around for quite a while and during multiple releases. SVN does a nice job in merging those things in when upgrading to another release - but nevertheless, they lure around in the source tree, without proper documentation, and tend to get forgotten.
So, one can either live with that, or think about a solution...
(*) and this is not the only one, see e.g. here, or here:
https://stackoverflow.com/questions/53715647/ruby-bundler-fails-with-errnoerofs
https://groups.google.com/forum/#!topic/bareos-users/lAlWhIdXPXk
Probably, these people tend to expect that one becomes a member of their specific developer communities (and adhere to their specific buerocracy), in order to deliver fixes - which then may or may not help the issue. But then, we have some 25'000 ports, and I definitely do not want to become member in dozens of whatever things, just because some coding error decides perchance to hop into my face so that I need to fix it.