[MacPorts] #54296: wxWidgets-3.0: fix issues after update to 3.0.3.1
MacPorts
noreply at macports.org
Sat Nov 4 10:36:56 UTC 2017
#54296: wxWidgets-3.0: fix issues after update to 3.0.3.1
-------------------------------------------------+-------------------------
Reporter: mojca | Owner: mojca
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: wxWidgets-3.0 wxgtk-3.0 p5-alien- |
wxwidgets p5-wx |
-------------------------------------------------+-------------------------
Comment (by mojca):
A branch behaves exactly the same as any other pull request. Once you are
in an existing clone, you just need to fetch the additional code.
Here's what I usually do (PR can be ignored):
{{{
# set these up for each individual commit (no need for GH_PR, it's just
for myself)
GH_PR=994
GH_USER=mojca
GB_REMOTEBR=wxWidgets-3.0.3
# everything below is copy-pasting
# LOCALBR is just how I want to name the branch myself locally
LOCALBR=pr${GH_PR}-${GH_USER}-${GH_REMOTEBR}
# fetch the remote branch (you can do the same even if there's not PR
open)
git fetch git://github.com/$GH_USER/macports-ports.git $GH_REMOTEBR
# check that out in a local branch (using the name you picked before)
git checkout -b $LOCALBR FETCH_HEAD
# optional, only relevant if you want to merge it or make sure you're
always on top
git rebase master
# if you want to modify someone else's branch for the sake of fixing a PR
git push -f https://github.com/$GH_USER/macports-ports.git
$LOCALBR:$GH_REMOTEBR
# if you want to push the changes to master
git push origin $LOCALBR:master
}}}
(Please note: I didn't copy-paste this time, I'm in the middle of
switching computers and retyping was just faster, just watch for any typos
before blindly copying everything :)
If you need a portindex, you can actually copy it from the main index
first and then you'll just need to process the changes. But yes, if you
want to test it, it probably makes sense to at least temporarily switch to
git completely. You can cheat if you only have one port, but it's easier
to go for the whole tree if there are multiple ports involved.
--
Ticket URL: <https://trac.macports.org/ticket/54296#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list