[notabug] Any interest in having updates/fixes to R-related ports here?

[barracuda156]

@RJVB As you probably know, I stopped submitting stuff to upstream MacPorts and just maintain a fork in a similar way to this one. While overall my fork is targeting PowerPC, everything R-related is not specific to either powerpc or legacy macOS and retains compatibility with modern macOS and clang. It should just work as a drop-in replacement, which provides more up-to-date ports.

Since, I think, nobody knows about my repo for R ports, and nobody gonna use my fork outside of PowerPC, I thought it could be useful to add it here.

It won’t be practical to go via PRs and dilute commit history with all that R stuff which is a niche thing, but perhaps it can be added as a link to either https://github.com/macos-powerpc/powerpc-ports/tree/main/R (only ports which diverge from mainstream) or https://github.com/macos-powerpc/R-ports/tree/main/R (complete subtree). Besides R directory only R port and R PG are needed, so the whole thing is pretty much standalone and won’t intervene with anything else.

P. S. I do not think R ports are of interest for you personally, but I am sure more people use macstrop, and there is no reason to restrict R updates to powerpc systems.

[RJVB]

On Monday March 03 2025 01:37:40 Sergey Fedorov wrote:

It won’t be practical to go via PRs and dilute commit history with all that R stuff which is a niche thing, but perhaps it can be added as a link to either https://github.com/macos-powerpc/powerpc-ports/tree/main/R (only ports which diverge from mainstream) or https://github.com/macos-powerpc/R-ports/tree/main/R (complete subtree). Besides R directory only R port and R PG are needed, so the whole thing is pretty much standalone and won’t intervene with anything else.

P. S. I do not think R ports are of interest for you personally, but I am sure more people use macstrop, and there is no reason to restrict R updates to powerpc systems.

I did use R extensively once, but that was in another life that I'm done with.

What do you mean with "added as a link"? I can add the R PG is it doesn't evolve too often but I'd prefer to keep the repo as light as possible.

[barracuda156]

What do you mean with "added as a link"?

I have seen here and there on GH that a directory in a repo can be included as a “symlink” pointing to another repo. (Perhaps what gets pulled in as submodules?)

I can add the R PG is it doesn't evolve too often but I'd prefer to keep the repo as light as possible.

It won’t be sensible to commit every R-related update here, of course. What I thought of is some way for it to become available for macstrop users without introducing any additional maintenance burden for you or myself. If there is no easy way to do that or if you do not think it is desirable, we just close the issue.

[RJVB]

I have seen here and there on GH that a directory in a repo can be included as a “symlink” pointing to another repo. (Perhaps what gets pulled in as submodules?)

Yes, submodules. Lemme think about whether I want to use those...

I'm not certain if those will get updated during port sync though.

[barracuda156]

I have actually decided to have R ports only as a standalone repo, without duplicating any ports in my PPCPorts repo. All R stuff is self-sufficient, so just adding rsync://macos-powerpc.org/macos-powerpc/R/R-ports.tar to sources.conf should work on any macOS version. So likewise, I now think it is unnecessary to duplicate it in MacStrop either.

If you will think R ports are useful, you may add an instruction to README. Either rsync or git way will work. I am closing the issue with this.

[RJVB]

If you will think R ports are useful, you may add an instruction to README. Either rsync or git way will work.

Thanks, I may add a "see also" section ;)