> On 13 Dec 2016, at 20:14, Mojca Miklavec wrote:
>
> On 13 December 2016 at 20:08, Luc Bourhis wrote:
>>
>>> (Ruby is completely outdated and only the interpreter works, packaging
>>> is completely unmaintained.
>>
>> MacPorts provide ruby 2.3, wh
Hi Mojca,
> On 13 December 2016 at 16:32, Luc Bourhis wrote:
>> Hi,
>>
>> I am writing an update for the fsharp port (F# language), which is very
>> outdated. This requires an update to the mono port, from version 3 to 4. One
>> could make the case to suppor
Hi,
I am writing an update for the fsharp port (F# language), which is very
outdated. This requires an update to the mono port, from version 3 to 4. One
could make the case to support every x.y version of Mono and F# as MacPorts
does for python, ruby, etc and then to let the user choose with po
>> 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
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
