From Fedora Project Wiki
(Open review requests: add resque-job-stats)
(Open review requests: literati is compmlete)
 
(19 intermediate revisions by the same user not shown)
Line 9: Line 9:
 
#* Bundler issues: If we use different Gem versions than upstream, Bundler wants to write to Gemfile and Gemfile.lock. We will use bundler_ext to work around this. This will require the {{Pkg|rubygem-bundler_ext}} package and a lot of testing.
 
#* Bundler issues: If we use different Gem versions than upstream, Bundler wants to write to Gemfile and Gemfile.lock. We will use bundler_ext to work around this. This will require the {{Pkg|rubygem-bundler_ext}} package and a lot of testing.
 
#* Init scripts: Create equivalent systemd unit files for Fedora & RHEL 7.
 
#* Init scripts: Create equivalent systemd unit files for Fedora & RHEL 7.
#* Ruby version: Upstream "next" branch works with Ruby 1.9.3 and 2.0.0. I'm working with upstream to maintain this compatibility via [https://ci.gitorious.org/jenkins/ Jenkins].
+
#* Ruby version: Upstream "master" branch works with Ruby 1.9.3 and 2.0.0. I'm working with upstream to maintain this compatibility via [https://ci.gitorious.org/jenkins/ Jenkins].
 
#* Gem versions: Upstream uses different Gem versions than Fedora has. The biggest difference is Rails, but others are documented below. Plan of attack is to ensure that the test suite passes with both.
 
#* Gem versions: Upstream uses different Gem versions than Fedora has. The biggest difference is Rails, but others are documented below. Plan of attack is to ensure that the test suite passes with both.
 
#* Javascript libs: There are several Git submodules in upstream (bane, capillary-js, raphael, spin.js, others). We must unbundle these and [[JavaScript libraries packaging guideline draft|package them]] separately.
 
#* Javascript libs: There are several Git submodules in upstream (bane, capillary-js, raphael, spin.js, others). We must unbundle these and [[JavaScript libraries packaging guideline draft|package them]] separately.
Line 20: Line 20:
 
#* Various Rubygems must be branched for EPEL.
 
#* Various Rubygems must be branched for EPEL.
 
# Get Gitorious into EPEL.
 
# Get Gitorious into EPEL.
#* Unfortunately upstream has dropped support for Ruby 1.8, so formal EPEL inclusion can only happen after RHEL 7 is released and EPEL 7 is branched.
+
#* Unfortunately upstream has dropped support for Ruby 1.8, so formal EPEL inclusion can only happen in EPEL 7.
  
 
== Open review requests ==
 
== Open review requests ==
Line 29: Line 29:
 
! Gem !! Package Review Request
 
! Gem !! Package Review Request
 
|-
 
|-
| climate_control || {{bz|1017994}}
+
| resque-cleaner || {{bz|1037278}}
|-
 
| unicorn || {{bz|786636}}
 
|-
 
| inflecto || {{bz|1036836}}
 
|-
 
| org-ruby || {{bz|1036901}}
 
 
|-
 
|-
| resque-cleaner || {{bz|1037278}}
+
| resque-job-stats || {{bz|1037900}}
 
|-
 
|-
| rubygem-resque-job-stats || {{bz|1037900}}
+
| paperclip || {{bz|1065682}}
 
|-
 
|-
 
|}
 
|}
Line 50: Line 44:
 
# <code>git clone git://gist.github.com/movitto/6086381 rhgc</code>
 
# <code>git clone git://gist.github.com/movitto/6086381 rhgc</code>
 
# <code>./rhgc/rhgc.rb --gemfile gitorious/Gemfile</code>
 
# <code>./rhgc/rhgc.rb --gemfile gitorious/Gemfile</code>
 
You will need rubygem-gemnasium-parser in order to run rhgc.rb, but this package is not yet in Fedora. You can find it here: http://ktdreyer.fedorapeople.org/rhgc/
 
  
 
== Gem dependency graph ==
 
== Gem dependency graph ==

Latest revision as of 21:07, 8 July 2014

This document outlines the steps to get Gitorious into Fedora and EPEL.

High Level Steps and Issues

Fedora

  1. Get all Gitorious' dependencies into Fedora.
    • Several Rubygems.
    • Several Javascripts.
  2. Get Gitorious into Fedora.
    • Bundler issues: If we use different Gem versions than upstream, Bundler wants to write to Gemfile and Gemfile.lock. We will use bundler_ext to work around this. This will require the rubygem-bundler_ext package and a lot of testing.
    • Init scripts: Create equivalent systemd unit files for Fedora & RHEL 7.
    • Ruby version: Upstream "master" branch works with Ruby 1.9.3 and 2.0.0. I'm working with upstream to maintain this compatibility via Jenkins.
    • Gem versions: Upstream uses different Gem versions than Fedora has. The biggest difference is Rails, but others are documented below. Plan of attack is to ensure that the test suite passes with both.
    • Javascript libs: There are several Git submodules in upstream (bane, capillary-js, raphael, spin.js, others). We must unbundle these and package them separately.
    • GeoIP data: Gitorious bundles GeoIP.dat, which is already available in Fedora as the "GeoIP" package.
    • FHS considerations: for the Gitorious web application itself, we need to discover how to split up the package to fit the FHS conventions of /etc/, /usr/, and so on.

EPEL

  1. Get all Gitorious's dependencies into EPEL.
    • Rails. I don't have experience packaging Rails, and there's been questions about which version to put into EPEL.
    • Various Rubygems must be branched for EPEL.
  2. Get Gitorious into EPEL.
    • Unfortunately upstream has dropped support for Ruby 1.8, so formal EPEL inclusion can only happen in EPEL 7.

Open review requests

Please review some of these. I'm willing to trade reviews.

Gem Package Review Request
resque-cleaner RHBZ #1037278
resque-job-stats RHBZ #1037900
paperclip RHBZ #1065682

Checking progress with rhgc.rb

In order to see the list of gems that must still be packaged:

  1. git clone git://gitorious.org/gitorious/mainline.git gitorious
  2. git clone git://gist.github.com/movitto/6086381 rhgc
  3. ./rhgc/rhgc.rb --gemfile gitorious/Gemfile

Gem dependency graph

You can view the outstanding Gem dependency chart (graphviz source). I will attempt to keep this graph up to date, but it is a manual process. For "live" data, see the rhgc.rb section above.

This graph does not take into account Javascript libraries.