Jordi Bunster

This is a workaround to now having this in Rails: http://gist.github.com/78259

Sadly, I can't really make it a plugin, because of how early in the initializatio...

If I may, I think you folks are looking for something like gems:vendor.

You can have gems:install, gems:unpack, gems:unpack:dependencies, etc, all stay the same...

Pratik: I know. I don't take it one way or another. Just trying to get the patch in. :P

Damian:

I think the service-specific part is the fact that when you pass :author (or :prepend or :whatever_color_the_shed_is) we then assume :source => GitHub.

Nicolás: yeah, I went for brevity, but I see your point. I wouldn't mind changing the syntax.

Pratik: I thought about it, but the reality is that more and more ...

José:

I did a quick search for the one you mentioned but I couldn't find it here on Lighthouse. Is it here, do you know?

Lately my environment.rb is filled with GitHub gems. I suspect yours is too.

I got a bit tired of all the :source and :lib stuff, so I whipped this patch to all...

I don't get this. Why would one conditionally create things in migrations?

Doesn't each one run over a consistent state?

+1

When I created the index I decided to use the add_index method instead of custom SQL, because I assumed it added the correct prefixes. I now see that it does...

That's a good point.

We only pass one version, and when rake db:schema:load runs, it assumes we've migrated all the way up to that. If it turns out that somehow...