Differences between revisions 1 and 2
Revision 1 as of 2008-03-08 17:05:36
Size: 1372
Comment: Initial revision
Revision 2 as of 2008-03-08 17:06:47
Size: 1367
Comment: shorter title, R URL
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= cran2deb: Generate Debian packages for R from package sources on CRAN and maybe BioConductor = = cran2deb: Generate Debian packages for R from package sources =
Line 3: Line 3:
 * '''Summary''': GNU R has become the preeminent platform for 'computing with data'. The [http://cran.r-project.org/web/packages CRAN] archives contain over 1300 source packages of very high-quality. We want more of these in Debian, and going beyond the 50+ packages we currently have suggests more scripting and automation.  * '''Summary''': [http://www.r-project.org GNU R] has become the preeminent platform for 'computing with data'. The [http://cran.r-project.org/web/packages CRAN] archives contain over 1300 source packages of very high-quality. We want more of these in Debian, and going beyond the 50+ packages we currently have suggests more scripting and automation.
Line 8: Line 8:
 * '''Description''': CRAN ppackages have in almost all cases licenses are suitable for Debian 'main'. Moreover, the internal packaging and structure of these packages already resembles some of the Debian meta-data, and the build process itself is standardised. What is needed are a set of tools to collect package meta-data (and the [http://dirk.eddelbuettel.com/cranberries/index.html CRANberries] aggregator has one-half, apt has the other), 'map' the meta-data and then script package fragments. While the [:AliothPkgBioc: PkgBioc project on Alioth] has done work in this area, it may be worthwhile to try a new and simpler approach.  * '''Description''': CRAN packages have in almost all cases licenses are suitable for Debian 'main'. Moreover, the internal packaging and structure of these packages already resembles some of the Debian meta-data, and the build process itself is standardised. What is needed are a set of tools to collect package meta-data (and the [http://dirk.eddelbuettel.com/cranberries/index.html CRANberries] aggregator has one-half, apt has the other), 'map' the meta-data and then script package fragments. While the [:AliothPkgBioc: PkgBioc project on Alioth] has done work in this area, it may be worthwhile to try a new and simpler approach.

cran2deb: Generate Debian packages for R from package sources

  • Mentor: DirkEddelbuettel

  • Summary: [http://www.r-project.org GNU R] has become the preeminent platform for 'computing with data'. The [http://cran.r-project.org/web/packages CRAN] archives contain over 1300 source packages of very high-quality. We want more of these in Debian, and going beyond the 50+ packages we currently have suggests more scripting and automation.

  • Required skills:

    • Familiarity with [http://www.r-project.org R], preferably actual programming experience

    • Programming experience in a scripting language (Perl, Python, ...)
    • C++ knowledge may be beneficial to connect to apt's data structures
  • Description: CRAN packages have in almost all cases licenses are suitable for Debian 'main'. Moreover, the internal packaging and structure of these packages already resembles some of the Debian meta-data, and the build process itself is standardised. What is needed are a set of tools to collect package meta-data (and the [http://dirk.eddelbuettel.com/cranberries/index.html CRANberries] aggregator has one-half, apt has the other), 'map' the meta-data and then script package fragments. While the [:?AliothPkgBioc: ?PkgBioc project on Alioth] has done work in this area, it may be worthwhile to try a new and simpler approach.