Skye Bender-deMoll
2014-Jun-13 21:41 UTC
[Rd] what is the current correct repos structure for mac osx binaries?
Dear R-developers, As part of our package building process, we maintain internal CRAN-like repositories of our packages. This has worked pretty well, but we are running into issues with R 3.1 and OSX mavericks. Specifically, machines with osx mavericks seem to, by default, expect packages to be located under a 'mavericks' sub-directory, but this is not the location reported when generating a mac.binary appropriate contrib url. >contrib.url('foo') [1] "foo/bin/macosx/mavericks/contrib/3.1/" If I ask where the mac binaries are on a linux machine (AND on mac mavericks machines) I get >contrib.url('foo',type='mac.binary') [1] "foo/bin/macosx/mavericks/contrib/3.1/" But the OSX machine gives an error and fails to locate the packages if they are located at foo/bin/macosx/contrib/3.1/ So where are the mac binaries supposed to located in a CRAN-like repository so that they can be installed on a mac with the default install command? And is there a way for a non-mac machine (i.e. our linux deploy server) to determine that directory other than contrib.url(,type='mac.binary) ? thanks for your help, -skye
Simon Urbanek
2014-Jun-14 00:22 UTC
[Rd] what is the current correct repos structure for mac osx binaries?
On Jun 13, 2014, at 5:41 PM, Skye Bender-deMoll <skyebend at skyeome.net> wrote:> Dear R-developers, > > As part of our package building process, we maintain internal CRAN-like repositories of our packages. This has worked pretty well, but we are running into issues with R 3.1 and OSX mavericks. > > Specifically, machines with osx mavericks seem to, by default, expect packages to be located under a 'mavericks' sub-directory, but this is not the location reported when generating a mac.binary appropriate contrib url. > > >contrib.url('foo') > [1] "foo/bin/macosx/mavericks/contrib/3.1/" > > > If I ask where the mac binaries are on a linux machine (AND on mac mavericks machines) I get > > >contrib.url('foo',type='mac.binary') > [1] "foo/bin/macosx/mavericks/contrib/3.1/" >I don't think that is true. On all machines (Linux, OS X, ...) I get> contrib.url('foo', type='mac.binary')[1] "foo/bin/macosx/contrib/3.1" Note that the type for the mavericks build is "mac.binary.mavericks", so on all machines you also get> contrib.url('foo',type='mac.binary.mavericks')[1] "foo/bin/macosx/mavericks/contrib/3.1" The only difference are the defaults for pkgType - they differ by the build, but the repo structure is fixed and consistent across all platforms. Cheers, Simon> > But the OSX machine gives an error and fails to locate the packages if they are located at foo/bin/macosx/contrib/3.1/ > > So where are the mac binaries supposed to located in a CRAN-like repository so that they can be installed on a mac with the default install command? And is there a way for a non-mac machine (i.e. our linux deploy server) to determine that directory other than contrib.url(,type='mac.binary) ? > > thanks for your help, > -skye > > ______________________________________________ > R-devel at r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel >
Possibly Parallel Threads
- issues with dev.new avoiding RStudio plot device on unix?
- alternatives to do.call() when namespace is attached but not loaded?
- issues with dev.new avoiding RStudio plot device on unix?
- what is the correct way to force a copy of an object?
- quieting the "apparent S3 methods" warning