[MacPorts] #69837: Redesign R ports/portgroup so that a revbump is not needed after major R updates
MacPorts
noreply at macports.org
Sat Apr 27 05:43:52 UTC 2024
#69837: Redesign R ports/portgroup so that a revbump is not needed after major R
updates
-------------------------+--------------------
Reporter: ryandesign | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: R |
-------------------------+--------------------
Comment (by barracuda156):
Replying to [comment:1 jmroot]:
> I'm not clear on why we even have 4,854 R ports. Is anyone using most of
them? Can't they be installed via CRAN? Python is one of the most popular
languages, and we have 2,278 entries in the python category, since we tend
not to package modules that can easily be installed with pip and aren't
needed by ports.
As you can see, many other downstream distributions have their ports for R
stuff instead of just relying on CRAN.
There are a few issues with using CRAN, some of which are easy to solve,
some perhaps non-trivial and some are completely breaking.
What we have is working better than CRAN.
Having said that, I agree that given what Ryan said, we should avoid
revbumps on minor version upgrades. So that will be done, I will deal with
this today.
--
Ticket URL: <https://trac.macports.org/ticket/69837#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list