Differences between revisions 2 and 31 (spanning 29 versions)
Revision 2 as of 2012-06-16 00:10:40
Size: 417
Comment:
Revision 31 as of 2012-06-28 01:47:07
Size: 2686
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 =
Line 4: Line 4:
is being used to coordinate out attempt. -- AntonioTerceiro is being used to coordinate our attempt. -- AntonioTerceiro
Line 6: Line 6:
TODO list == TODO list ==
Line 9: Line 9:
   * /!\ 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]] ''waiting in NEW''
     * upload version 1.1 after 1.0 passes NEW !!!
   * {*} 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!
       * :o ruby-sprockets is 2.4.x, while the actionpack gemspec requires 2.1.x !!!!
 * review railties after Debian packages are recognizable by Rubygems
Line 10: Line 22:
   * pkg1
   * pkg2
   * pkg3
   * pkg4
   * pkg5
   * pkg6
   * pkg7
   * /!\ jquery-rails (2.0.2) ''waiting in NEW''
   * --(rdoc)-- ''not actually needed, provided by ruby''
   * coffee-script-source ''WIP - terceiro''
   * execjs ''WIP - terceiro''
     * 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 ''WIP - terceiro''
     * must be patched to use the existing coffeescript from libjs-coffeescript)
   * coffee-rails ''WIP - terceiro''
   * sass-rails ''WIP - gramos''
   * uglifier ''WIP - terceiro''
Line 18: Line 34:
   * master bug preventing the entire rails 3 stack from entering testing: DebianBug:674518
Line 19: Line 36:


== Rails 3 testcase ==

 * Create an empty application
   * the Gemfile must be same as the one created by rails installed via rubygems
   * yet nothing should be downloaded via rubygems/bundler
   * you must be able to boot the application
     * rails console
     * rails server
   * remove public/index.html
   * add a welcome controller and point the root to its index
 * acessing / must work
   * jquery and jquery_ujs must be referenced in the page header
 * rake assets:precompile must work

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 waiting in NEW

      • upload version 1.1 after 1.0 passes NEW !!!
    • {*} 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!
        • :o ruby-sprockets is 2.4.x, while the actionpack gemspec requires 2.1.x !!!!

  • review railties after Debian packages are recognizable by Rubygems
  • Package missing dependencies:
    • /!\ jquery-rails (2.0.2) waiting in NEW

    • rdoc not actually needed, provided by ruby

    • coffee-script-source WIP - terceiro

    • execjs WIP - terceiro

      • 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 WIP - terceiro

      • must be patched to use the existing coffeescript from libjs-coffeescript)
    • coffee-rails WIP - terceiro

    • sass-rails WIP - gramos

    • uglifier WIP - terceiro

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

    • bug links here

Rails 3 testcase

  • Create an empty application
    • the Gemfile must be same as the one created by rails installed via rubygems
    • yet nothing should be downloaded via rubygems/bundler
    • you must be able to boot the application
      • rails console
      • rails server
    • remove public/index.html
    • add a welcome controller and point the root to its index
  • acessing / must work
    • jquery and jquery_ujs must be referenced in the page header
  • rake assets:precompile must work