On 2016-12-14 00:19 , Luc Bourhis wrote:
On 13 Dec 2016, at 14:13, Joshua Root <j...@macports.org> wrote:
On 2016-12-13 23:56 , Luc Bourhis wrote:
I was considering to only fork macports-ports so that I can use pull requests
for ports, without having to build macports core from source. But then what is
the best way to configure macports on my system? Shall I replace the line
rsync://rsync.macports.org/release/tarballs/ports.tar [default]
in sources.conf with
file://path/to/my/clone/of/macports-ports [default]
or is there a better alternative?
That would work fine, yes.
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>.
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.
- Josh
