Ruby Forum Rails-core > Rick's gems:freeze plugin -> core

Posted by Dr Nic (nicwilliams)
on 12.10.2006 16:27
(Received via mailing list)
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.
Posted by Michael Koziarski (Guest)
on 18.10.2006 10:40
(Received via mailing list)
> 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
Posted by Rick Olson (Guest)
on 18.10.2006 10:40
(Received via mailing list)
> 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
Posted by Dr Nic (nicwilliams)
on 18.10.2006 10:40
(Received via mailing list)
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:
> This is the chunk of code I'm referring to:
> >
>


--
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)
Posted by Dr Nic (nicwilliams)
on 18.10.2006 10:40
(Received via mailing list)
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
Posted by Michael Koziarski (Guest)
on 18.10.2006 10:44
(Received via mailing list)
> 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
Posted by Jamis Buck (Guest)
on 18.10.2006 10:44
(Received via mailing list)
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
Posted by Michael Koziarski (Guest)
on 18.10.2006 10:44
(Received via mailing list)
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
Posted by DHH (Guest)
on 18.10.2006 10:44
(Received via mailing list)
> 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).
Posted by Thijs Cadier (thijsc)
on 18.10.2006 10:44
(Received via mailing list)
There is a difference though, gems:freeze is really new functionality
and ARTS is a proper way to test existing functionality.
Posted by Dr Nic (nicwilliams)
on 18.10.2006 10:44
(Received via mailing list)
I've no issue with gems:freeze waiting til post-1.2.

Nic

On 10/14/06, Thijs Cadier / 80beans <thijs@80beans.com> wrote:
> >> wait.
>
--
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)
Posted by James Adam (Guest)
on 18.10.2006 10:44
(Received via mailing list)
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 *
  ~
Posted by Mislav MarohniÄ? (mislav)
on 18.10.2006 10:44
(Received via mailing list)
"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.
Posted by Dr Nic (nicwilliams)
on 18.10.2006 10:44
(Received via mailing list)
Dr Nic wrote:
> 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