Rails Ruby on Rails → 3.x

Comments and changes to this ticket

• 

  Pratik January 23rd, 2009 @ 09:17 PM

  • Tag changed from “gems, rake” to “gems, patch, rake”
  • Assigned user set to “Matt Jones”
• 

  José Valim January 24th, 2009 @ 08:21 AM

  +1

• 

  Matt Jones January 25th, 2009 @ 11:26 PM

  -1 on this; haven't tested it, but it will most likely cause some spectacular failures in edge cases. Notably, one of the primary gems that needs building in many apps is RedCloth; it gets pulled in by Rails under some conditions on loading the environment, and dies messily (Bus error, on OSX) if the native support isn't present. That's the whole reason that the environment isn't loaded by the gems:build task...

  This is really part of #1721; the whole idea needs to be restructured.

• You flagged this item as spam.
  

  David Dollar March 27th, 2009 @ 07:07 PM

  This should no longer be an issue as of 2.3

• 

  Jeremy Kemper May 4th, 2010 @ 06:48 PM

  • Milestone changed from “2.x” to “3.x”

  [bulk edit]

• 

  Santiago Pastorino February 2nd, 2011 @ 04:42 PM

  • State changed from “new” to “open”
  • Importance changed from “” to “”

  This issue has been automatically marked as stale because it has not been commented on for at least three months.

  The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

  Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.

• 

  Santiago Pastorino February 2nd, 2011 @ 04:42 PM

  • State changed from “open” to “stale”