Thank you. I found out later that this issue was also reported on the bug tracker a while ago, so I think that can be closed now: https://bugs.r-project.org/show_bug.cgi?id=18330
On Tue, Nov 12, 2024 at 9:27 PM Simon Urbanek <simon.urba...@r-project.org> wrote: > > Jeroen, > > yes, you're right, that is incorrect. It should read "binary" as that is the > only value that automatically picks the correct binary repository for the > current R build regardless of platform. Or it should say > "mac.binary.big-sur-x86_64" corresponds to bin/macosx/big-sur-x86_64/contrib > and "mac.binary.big-sur-arm64" to bin/macosx/big-sur-arm64/contrib since the > rule is "mac.binary[.XXX]" corresponds to bin/macosx[/XXX]/contrib and thus > "mac.binary" is bin/macosx/contrib which has been used for the high-sierra > build, but is not correct for the (current) big-sur builds. The user > shouldn't really be manually specifying the build name, so that's why I'd not > mention "mac.binary" and only point to "binary" as that is what users should > be using. > > Cheers, > Simon > > > > On Nov 12, 2024, at 3:38 AM, Jeroen Ooms <jeroeno...@gmail.com> wrote: > > > > The R-admin manual section 6.6 talks about "mac.binary" to refer to > > macos binary packages but I don't think this is working. On R-4.4.2: > > > > contrib.url(repos = 'https://cran.r-project.org', type = 'mac.binary') > > # "https://cran.r-project.org/bin/macosx/contrib/4.4"; > > > > This URL is 404 because it is missing the /big-sur-arm64/ dir in the > > path. For the same reason we get an error: > > > > install.packages('MASS', type = 'mac.binary') > > > > I think in practice only type = "both" currently finds the correct > > binary packages? > > > > _______________________________________________ > > R-SIG-Mac mailing list > > R-SIG-Mac@r-project.org > > https://stat.ethz.ch/mailman/listinfo/r-sig-mac > > > _______________________________________________ R-SIG-Mac mailing list R-SIG-Mac@r-project.org https://stat.ethz.ch/mailman/listinfo/r-sig-mac
