Differences between revisions 1 and 24 (spanning 23 versions)
Revision 1 as of 2012-06-16 00:08:20
Size: 208
Comment:
Revision 24 as of 2012-06-25 00:24:54
Size: 1997
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Getting Rails 3 into Debian wheezy - coordination page = Getting Rails 3 into Debian wheezy - coordination page =

DISCLAIMER: we don't know if it will be possible to get Rails 3 on wheezy. Nevertheless, this page
is being used to coordinate our attempt. -- AntonioTerceiro
Line 5: Line 8:
* metapackages: ruby-rails-3.2 + rails3
* Package missing dependencies:
** pkg1
** pkg2
** pkg3
** pkg4
** pkg5
** pkg6
** pkg7
 * metapackages: ruby-rails-3.2 + rails3
   * /!\ uploaded, waiting for NEW processing.
 * Make Debian packages recognizable by Rubygems - this is necessary because of the way Rails uses bundler to declare application dependencies '''and''' load them at the right time. It will require overriding the Rubygems path and modifying dh_ruby to install a .gemspec file. ''WIP - terceiro''
   * --(change gem2deb to install gemspec)--
   * --(upload this new gem2deb)--
   * upload [[http://anonscm.debian.org/gitweb/?p=pkg-ruby-extras/rubygems-integration.git;a=summary|rubygems-integration]]
     * /!\ done, waiting for NEW processing.
   * {*} mass upload of all packages depending on gem2deb
     * see [[http://lists.debian.org/debian-ruby/2012/06/msg00097.html|this thread]]
     * Look out for relevant exceptions:
       * none of more common the database drivers (ruby-sqlite3, ruby-mysql, ruby-pg) have gemspecs!
 * review railties after Debian packages are recognizable by Rubygems
 * Package missing dependencies:
   * jquery-rails (2.0.2) ''WIP - terceiro''
   * --(rdoc)-- ''not actually needed, provided by ruby''
   * --(coffee-script-source)-- ''not needed (see coffee-script below)''
   * execjs
     * depends on a Javascript runtime. Node.js might not get into Wheezy, but maybe we can get execjs to work fine under gjs.
     * execjs also supports spidermonkey, but the spidermonkey adapter is marked as deprecated (why is that?)
   * coffee-script
     * must be patched to use the existing coffeescript from libjs-coffeescript)
   * coffee-rails
   * sass-rails ''WIP - gramos''
   * uglifier
 * bugs
   * master bug preventing the entire rails 3 stack from entering testing: DebianBug:674518
   * bug links here

Getting Rails 3 into Debian wheezy - coordination page

DISCLAIMER: we don't know if it will be possible to get Rails 3 on wheezy. Nevertheless, this page is being used to coordinate our attempt. -- AntonioTerceiro

TODO list

  • metapackages: ruby-rails-3.2 + rails3
    • /!\ uploaded, waiting for NEW processing.

  • Make Debian packages recognizable by Rubygems - this is necessary because of the way Rails uses bundler to declare application dependencies and load them at the right time. It will require overriding the Rubygems path and modifying dh_ruby to install a .gemspec file. WIP - terceiro

    • change gem2deb to install gemspec

    • upload this new gem2deb

    • upload rubygems-integration

      • /!\ done, waiting for NEW processing.

    • {*} mass upload of all packages depending on gem2deb

      • see this thread

      • Look out for relevant exceptions:
        • none of more common the database drivers (ruby-sqlite3, ruby-mysql, ruby-pg) have gemspecs!
  • review railties after Debian packages are recognizable by Rubygems
  • Package missing dependencies:
    • jquery-rails (2.0.2) WIP - terceiro

    • rdoc not actually needed, provided by ruby

    • coffee-script-source not needed (see coffee-script below)

    • execjs
      • depends on a Javascript runtime. Node.js might not get into Wheezy, but maybe we can get execjs to work fine under gjs.
      • execjs also supports spidermonkey, but the spidermonkey adapter is marked as deprecated (why is that?)
    • coffee-script
      • must be patched to use the existing coffeescript from libjs-coffeescript)
    • coffee-rails
    • sass-rails WIP - gramos

    • uglifier
  • bugs
    • master bug preventing the entire rails 3 stack from entering testing: 674518

    • bug links here