Has there been discussion about Rick Olsen''s gems plugin (http://www.agilewebdevelopment.com/plugins/gems) from being included into core? If not... Can we include Rick''s gems plugin code (a task and <10 lines of code) into core please? If yes, I''ll whip up a patch. Its generic and wonderful. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core -~----------~----~----~----~------~----~------~--~---
> Has there been discussion about Rick Olsen''s gems plugin > (http://www.agilewebdevelopment.com/plugins/gems) from being included > into core? > > If not... > > Can we include Rick''s gems plugin code (a task and <10 lines of code) > into core please? If yes, I''ll whip up a patch. > > Its generic and wonderful.Perhaps rick can share his thoughts, assuming it''s nice and seamless, I have no objections. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core -~----------~----~----~----~------~----~------~--~---
> Perhaps rick can share his thoughts, assuming it''s nice and seamless, > I have no objections.The actual gem:freeze task itself is very handy IMO. The only part I''m unsure of is the code that automatically inserts vendor/* folders into the LOAD_PATH. I assume if you use the gems plugin you want this, but I don''t know if it''s a good assumption to make for all apps. This is the chunk of code I''m referring to: http://svn.techno-weenie.net/projects/mephisto/trunk/vendor/plugins/a_gems/init.rb Thoughts? -- Rick Olson http://weblog.techno-weenie.net http://mephistoblog.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core -~----------~----~----~----~------~----~------~--~---
At the moment I''m investigating a structure for supporting tasks in gems being applied to rails apps. Give me a few days to think about this a bit. Nic On 10/13/06, Rick Olson <technoweenie@gmail.com> wrote:> > > > Perhaps rick can share his thoughts, assuming it''s nice and seamless, > > I have no objections. > > The actual gem:freeze task itself is very handy IMO. The only part > I''m unsure of is the code that automatically inserts vendor/* folders > into the LOAD_PATH. I assume if you use the gems plugin you want > this, but I don''t know if it''s a good assumption to make for all apps. > > This is the chunk of code I''m referring to: > > http://svn.techno-weenie.net/projects/mephisto/trunk/vendor/plugins/a_gems/init.rb > > Thoughts? > > -- > Rick Olson > http://weblog.techno-weenie.net > http://mephistoblog.com > > > >-- Dr Nic Williams http://www.drnicwilliams.com - Ruby/Rails blog skype: nicwilliams (m) +31 62 494 8552 (p) +61 7 3102 3237 (finds me anywhere in the world) (f) +61 7 3305 7572 (sends fax to my email) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core -~----------~----~----~----~------~----~------~--~---
Rick Olson wrote:> > Perhaps rick can share his thoughts, assuming it''s nice and seamless, > > I have no objections. > > The actual gem:freeze task itself is very handy IMO. The only part > I''m unsure of is the code that automatically inserts vendor/* folders > into the LOAD_PATH. I assume if you use the gems plugin you want > this, but I don''t know if it''s a good assumption to make for all apps.It might be cleaner to dump the gems in /vendor/gems and thus load them confidently from there. Nic --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core -~----------~----~----~----~------~----~------~--~---
> It might be cleaner to dump the gems in /vendor/gems and thus load them > confidently from there.Yeah, that would seem to be a nice, safe option. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core -~----------~----~----~----~------~----~------~--~---
For now, I think I''d like to suggest that we hold off on adding any more features to 1.2. Let''s get 1.2 stable and then talk about what to add to the next release. To that end, I think both gems:freeze and the ARTS stuff ought to wait. - Jamis On Oct 13, 2006, at 7:06 PM, Michael Koziarski wrote:> >> It might be cleaner to dump the gems in /vendor/gems and thus load >> them >> confidently from there. > > Yeah, that would seem to be a nice, safe option. > > -- > Cheers > > Koz > > --~--~---------~--~----~------------~-------~--~----~ > You received this message because you are subscribed to the Google > Groups "Ruby on Rails: Core" group. > To post to this group, send email to rubyonrails-core@googlegroups.com > To unsubscribe from this group, send email to rubyonrails-core- > unsubscribe@googlegroups.com > For more options, visit this group at http://groups.google.com/ > group/rubyonrails-core > -~----------~----~----~----~------~----~------~--~--- >
On 10/14/06, Jamis Buck <jamis@37signals.com> wrote:> For now, I think I''d like to suggest that we hold off on adding any > more features to 1.2. Let''s get 1.2 stable and then talk about what > to add to the next release. > > To that end, I think both gems:freeze and the ARTS stuff ought to wait.I think that''s a mighty fine idea, neither plugin is monkeypatching too heavily, so they''re unlikely to get busted by a 1.2 release. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core -~----------~----~----~----~------~----~------~--~---
> To that end, I think both gems:freeze and the ARTS stuff ought to wait.+1. We have a finite list of things we want done before release now. Otherwise this will just be the never ending story (II, the one that sucked). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core -~----------~----~----~----~------~----~------~--~---
There is a difference though, gems:freeze is really new functionality and ARTS is a proper way to test existing functionality. On 14-okt-2006, at 5:34, DHH wrote:> >> To that end, I think both gems:freeze and the ARTS stuff ought to >> wait. > > +1. We have a finite list of things we want done before release now. > Otherwise this will just be the never ending story (II, the one that > sucked). > > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core -~----------~----~----~----~------~----~------~--~---
I''ve no issue with gems:freeze waiting til post-1.2. Nic On 10/14/06, Thijs Cadier / 80beans <thijs@80beans.com> wrote:> > > There is a difference though, gems:freeze is really new functionality > and ARTS is a proper way to test existing functionality. > > > On 14-okt-2006, at 5:34, DHH wrote: > > > > >> To that end, I think both gems:freeze and the ARTS stuff ought to > >> wait. > > > > +1. We have a finite list of things we want done before release now. > > Otherwise this will just be the never ending story (II, the one that > > sucked). > > > > > > > > > > > >-- Dr Nic Williams http://www.drnicwilliams.com - Ruby/Rails blog skype: nicwilliams (m) +31 62 494 8552 (p) +61 7 3102 3237 (finds me anywhere in the world) (f) +61 7 3305 7572 (sends fax to my email) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core -~----------~----~----~----~------~----~------~--~---
On 10/13/06, DHH <david.heinemeier@gmail.com> wrote:> Otherwise this will just be the never ending story (II, the one that > sucked).Are we to take from this that you actually *liked* the first one? :) -- * J * ~ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core -~----------~----~----~----~------~----~------~--~---
"Neverending story" - the book - was actually great! It was the movie that sucked; even the author said that, embarrassed he sold the rights in the first place. On 10/14/06, James Adam <james.adam@gmail.com> wrote:> > > On 10/13/06, DHH <david.heinemeier@gmail.com> wrote: > > Otherwise this will just be the never ending story (II, the one that > > sucked). > > Are we to take from this that you actually *liked* the first one? :)--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core -~----------~----~----~----~------~----~------~--~---
Dr Nic wrote:> Rick Olson wrote: > > > Perhaps rick can share his thoughts, assuming it''s nice and seamless, > > > I have no objections. > > > > The actual gem:freeze task itself is very handy IMO. The only part > > I''m unsure of is the code that automatically inserts vendor/* folders > > into the LOAD_PATH. I assume if you use the gems plugin you want > > this, but I don''t know if it''s a good assumption to make for all apps. > > It might be cleaner to dump the gems in /vendor/gems and thus load them > confidently from there.The upside of all gems going into a separate folder is we can easily find all rake tasks: Add to rails/lib/tasks/rails.rb: Dir["./vendor/gems/*/**/*.rake"].sort.each { |ext| load ext } Rails-trac ticket: http://dev.rubyonrails.org/ticket/6410 * This ticket is just for the above trivial change, and not gems:freeze as a whole * Nic --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core -~----------~----~----~----~------~----~------~--~---