Best practice for port contributors in github world
Luc Bourhis
luc_j_bourhis at mac.com
Tue Dec 13 13:35:14 CET 2016
>> Thanks. Do I need to run `portindex` in that directory //path/to/my/clone/of/macports-ports ?
>
> Yes, although that will be done for you as part of 'port sync' (which is part of selfupdate).
>
>>> Another option is to have a repo with just the ports you're working on and set it up as per <https://guide.macports.org/chunked/development.local-repositories.html <https://guide.macports.org/chunked/development.local-repositories.html>>.
>>
>> This is my current setup actually. Which bring the next question: is it enough to just do `port selfupdate` after making the change above in sources.conf?
>
> Depends on how you have your remotes set up I guess. The command run by sync is 'git pull --rebase', so set it up so that will pull the changes you want.
Great! You are saving me a lot of time!
Thanks a bunch, Joshua,
Luc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20161213/5f96c0bd/attachment.html>
More information about the macports-dev
mailing list