[Rd] Creating RPMs for Packages

From: Max Kuhn <mxkuhn_at_gmail.com>
Date: Wed, 06 Jan 2010 13:35:17 -0500

My company is trying to manage R installations across a number large SMP machines. We're thinking out the best way to manage the packages installs and updates. They would be happy if we could work out RPM's for package installations (traceable, easily facilitated with existing sw management tools).

I don't know a lot and RPMs beyond how to use them, but it seems plausible to write R code to create the RPM package. If we need to update package X, which triggers and update of ancillary packages Y and Z, it should be possible to use available.packages() to figure out the dependencies, download the sources, write out the RPM headers and package things up.

Before I try to write any code, does anyone see any issues with this (or has it already been done)? Is this a ridiculous approach?



R-devel_at_r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel Received on Wed 06 Jan 2010 - 18:40:14 GMT

Archive maintained by Robert King, hosted by the discipline of statistics at the University of Newcastle, Australia.
Archive generated by hypermail 2.2.0, at Thu 07 Jan 2010 - 23:00:11 GMT.

Mailing list information is available at https://stat.ethz.ch/mailman/listinfo/r-devel. Please read the posting guide before posting to the list.

list of date sections of archive