[MacPorts] #59563: mariadb-10.2: configure.cxxflags-append -std=c++11 # plus `port bump`

[MacPorts]

#59563: mariadb-10.2: configure.cxxflags-append -std=c++11 # plus `port bump`
---------------------------+-----------------------
  Reporter:  vike2000      |      Owner:  michaelld
      Type:  defect        |     Status:  assigned
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.6.2
Resolution:                |   Keywords:  haspatch
      Port:  mariadb-10.2  |
---------------------------+-----------------------

Comment (by vike2000):

 Replying to [comment:3 ryandesign]:
 > Your patch also changes the checksums, which does not seem related to
 this ticket.
 Without bumping checksums it wouldn't build regardless of the other patch
 hunk.\\
 Cause this port is ahead of its main non-version-named port mariadb
 (latest sync `@5.5.65`),\\
 I sort of assumed this port had some implicit unstable dev/beta status.
 However bad a defense,\\
 this is not the first time i've had to bump checksums (non-semver-ish
 upstream updates a reason?),\\
 albeit in so blindly trusting any sources...

 Filing the ticket I mainly looked at
 [https://guide.macports.org/#project.contributing.updates],\\
 but also [https://guide.macports.org/#development.patches.portfile
 …#development.patches.portfile],
 and reading on under the next subheading
 [https://guide.macports.org/#development.patches.portfile
 …#development.patches.portfile],\\
 I remember the point that one “should create one patch file for each
 logical change that needs to be applied”.\\
 Am I amiss still considering this a border case?

 Would you suggest to make two different patch files in future similar
 cases?

-- 
Ticket URL: <https://trac.macports.org/ticket/59563#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS