-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
minetest rev2 & fix irrlicht 1.9.0mt8 #17241
Conversation
Notifying maintainers: |
ERROR - This is somewhat unexpected.
AFAIK the a.m. test build should have combined IrrlichtMt 1.9.0.9 with MT 5.6.1-MacPorts-rev2 However, I have to check again as the port install of MT could have just grabbed the 1.9.0mt8 and thus ignored the new IrrlichtMt 1.9.0.9 build apparently. Anyway not a big problem and I will introduce the a.m. fixes to 1.9.0mt8 as backport. Yep my fault and should have checked with
A good learning experience again. @l2dy - Sorry for the newbie noise produced by me. Back to the drawing board ... |
* backport fixes to irrlicht 1.9.0mt8 * amend MT 5.6.1 rev2 * introduce new variants: [+]GLES, benchmark, debug, gprof, noclient, psql, server * fix minetest/irrlicht#152 * introduce irrlichtmt rev1 * Fix01: irrlichtmt fails to install on Mac OS 10.6 <https://trac.macports.org/ticket/66439> * Fix02: minetest arm64 support <https://trac.macports.org/ticket/66600>
5b03f3b
to
3d0ad5b
Compare
Ready for review... And the skeletons in the drawer are: |
@aeiouaeiouaeiouaeiouaeiouaeiou Pleeeeeeeeeaaaaaaase kindly consider approval of review on basis of my a.m. resolve. Anyway there will be another day with "minetest" rev3 in the future, I presume. |
You should split this commit into 2, following the Commit Message Guidelines. Here are some git commands for your reference, with # in repository root with a clean working tree
git reset --mixed HEAD~1
git commit -m 'irrlichtmt: xxxx' -- devel/irrlichtmt
git commit -m 'minetest: xxxx' -- games/minetest
git push -f Edit: 1 is the number of commits to move backwards in history, in your PR there is 1. |
@l2dy - Sorry, but let me ask what was your message in "combining and commit on top" before?
@l2dy - THX - 😮💨 May the Port be with you. 🤣 Apparently, I totally misunderstood and naturally I am to blame and my job of learning and improving as new maintainer. Don't want to be a bother to you, however, I sincerely would have preferred some more clarity in your before message. Anyway, I already made it much more challenging to you and reviewers due to:
Resolving to a new approach with several new ports & Portfiles for both 'ircchlichtmt' and 'minetest' respectively. There will be fun. 🌻 |
A PR could be made from a branch that has more than one commits to be merged. In most cases, it's recommended to isolate changes of different ports into different commits and stack them on top of each other in their order of dependency relationship. If for any reason this is not feasible, you should still follow the "List any modified ports in Subject" rule and start your commit message with |
Old News
Good advice for some future use, I guess. This PR was closed and the branch was deleted one hour ago. New DealOn to a new approach with several new ports & Portfiles for both 'irrlichtmt' and 'minetest' respectively and independent commits. All this although a quite interdependent change to both ports will hopefully happen soon. There will be fun. 🌻 |
This PR was obsoleted by
Description
Combined amend minetest rev2 & fix irrlicht 1.9.0mt8 rev1
ref minetest/irrlicht#152
Type(s)
Tested on
macOS 11.7.2 20G1020 x86_64
Command Line Tools 13.2.0.0.1.1638488800
Verification
Have you
port lint --nitpick
?sudo port -vst install
?Future tasks:
The b.m. Trac ticket should not hinder any review and is an independent activity by same maintainer: