Differences between revisions 34 and 35
Revision 34 as of 2012-06-28 11:50:13
Size: 3075
Revision 35 as of 2012-06-28 12:22:24
Size: 3027
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
 * metapackages: ruby-rails-3.2 + rails3
   * /!\ uploaded, waiting for NEW processing.
 * --(metapackages: ruby-rails-3.2 + rails3)--
Line 13: Line 12:
   * /!\ 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 !!!
   * --(upload [[http://anonscm.debian.org/gitweb/?p=pkg-ruby-extras/rubygems-integration.git;a=summary|rubygems-integration]])--
   * new upload of rubygems-integration (version 1.1)
Line 25: Line 24:
   * execjs ''WIP - terceiro''    * /!\ execjs ''waiting in NEW''
Line 32: Line 31:
   * uglifier ''WIP - terceiro''    * /!\ uglifier ''waiting in NEW''

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

  • 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

    • new upload of rubygems-integration (version 1.1)
    • {*} 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 waiting in NEW

    • /!\ execjs waiting in NEW

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

  • make sure that installing rails3 with rails (2.3) installed works (i.e. rails and its components are removed in favor of rails3 and its components).
    • also make sure the inverse also works (i.e. installing rails (2.3) while having rails3 installed)
  • 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
  • ?CoffeeScript files must be properly compiled to Javascript and run

  • SASS files must be properly compiled to CSS and used