> On Dec 13, 2016, at 7:56 AM, Luc Bourhis wrote:
>
> file://path/to/my/clone/of/macports-ports [default]
Note that you have to use three slashes at the beginning of this line because
the "/" that begins the absolute path is distinct from the "://" that separates
the protocol. So:
file:///pat
>> 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
On 2016-12-14 00:19 , Luc Bourhis wrote:
On 13 Dec 2016, at 14:13, Joshua Root 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
On 2016-12-13 23:56 , Luc Bourhis wrote:
Hi,
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.mac
Hi,
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 [defau
