Bug 201828 - [new port] www/rubygem-rails41
Summary: [new port] www/rubygem-rails41
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Martin Wilke
URL:
Keywords:
Depends on: 201815 201816 201817 201818 201819 201820 201822 201823 201825 201826 201829 201830
Blocks:
  Show dependency tree / graph
 
Reported: 2015-07-24 14:03 UTC by Torsten Zühlsdorff
Modified: 2016-01-04 09:25 UTC (History)
4 users (show)

See Also:

Attachments
rubygem-rails41.shar (6.78 KB, text/plain)
2015-07-24 14:03 UTC, Torsten Zühlsdorff 		no flags Details
Shar with rails 4.1.13 (4.10 KB, text/plain)
2015-09-03 15:41 UTC, Torsten Zühlsdorff 		no flags Details
Shar with rails 4.1.14 (4.10 KB, text/plain)
2015-11-23 10:58 UTC, Torsten Zühlsdorff 		no flags Details
Show Obsolete (2) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Torsten Zühlsdorff 2015-07-24 14:03:40 UTC 

    


    


      



        
          Comment 1
        

        
          Torsten Zühlsdorff

        

        
        

        
          2015-07-24 14:03:42 UTC
        

      






Created attachment 159162 [details]
rubygem-rails41.shar

    


    


      



        
          Comment 2
        

        
          Torsten Zühlsdorff

        

        
        

        
          2015-07-24 14:20:55 UTC
        

      






Bringing back Rails 4.1 into portstree. :)

Even if its older many rubygems depends on it. And there are various problems when using Rails 4.2 + instead. Therefore we need the possibility to use Rails 4.1 when needed.

    


    


      



        
          Comment 3
        

        
          Johannes Jost Meixner

        

        
            freebsd_committer
            freebsd_triage
        

        
          2015-07-24 14:32:04 UTC
        

      






add swills@ and sunpoet, mark as open.

I've discussed creating (or better, resurrecting) the rubygem-rails41 port with Torsten via email.

    


    


      



        
          Comment 4
        

        
          Philip M. Gollucci

        

        
            freebsd_committer
            freebsd_triage
        

        
          2015-08-25 20:38:55 UTC
        

      






Take.

    


    


      



        
          Comment 5
        

        
          Torsten Zühlsdorff

        

        
        

        
          2015-09-03 15:41:26 UTC
        

      






Created attachment 160674 [details]
Shar with rails 4.1.13

After the needed dependencies were already updated to 4.1.13 the old shar wont work anymore. This update fixes this and update the port to the newest version.

    


    


      



        
          Comment 6
        

        
          Torsten Zühlsdorff

        

        
        

        
          2015-11-23 10:58:20 UTC
        

      






Created attachment 163454 [details]
Shar with rails 4.1.14

There was already a second update of the dependencies to 4.1.14. The shar wont work anymore, therefore i wrote an update of this port to the current version 4.1.14.

    


    


      



        
          Comment 7
        

        
          Martin Wilke

        

        
            freebsd_committer
            freebsd_triage
        

        
          2015-12-19 07:04:42 UTC
        

      






Going to take care of this.

    


    


      



        
          Comment 8
        

        
          Torsten Zühlsdorff

        

        
        

        
          2016-01-04 09:25:26 UTC
        

      






I'm closing this PR, because Rails 4.1 was just created to allow the creation of the new port www/gitlab. GitLab itself switches in december 2015 to Rails 4.2, so this PR is no longer needed!

Also there is already a Beta for Rails 5. When Rails 5 will be released verson 4.1 will be unsupported through policy of Rails. Therefore there is no need to keep this old version!