bundling dependencies & source control problem

[Mr_Tibs]

Hi,

I bundled the dependencies of my merb app with thor which created the
cache, doc, gems and specifications directories under gems. I then
added all these directories (recursively) to source control. I'm using
svn. I then proceeded to deploy my application to production, which
performed "/bin/thor merb:gem:redeploy" in order to compile the native
gems.

The redeploy thor task did nothing because, I guess, the gems/gems
directories already exist and it thinks it doesn't need to recompile
the gems. So, after you bundle the dependencies, do you only add the
gems/cache directory to source control? You won't have access to thor
in that case, since ./bin/thor uses ./gems/gems/thor. So, what is the
correct setup for source control?

I have one other quick question to an issue that I came across when
compiling the native gems on the remote machine: does module do_mysql
compile with mysql 4.1 libraries?

Thanks,
Tiberiu

[Yehuda Katz]

You need ruby, rubygems, and thor on the remote machine.

-- Yehuda

2009/2/27 Mr_Tibs <tiberi...@gmail.com>

--
Yehuda Katz
Developer | Engine Yard
(ph) 718.877.1325

[Yehuda Katz]

2009/2/27 Mr_Tibs <tiberi...@gmail.com>

Probably not.
 

Thanks,
Tiberiu

[Alex Coles]

On Sat, Feb 28, 2009 at 3:10 AM, Mr_Tibs <tiberi...@gmail.com> wrote:

>
> ...

>
> I have one other quick question to an issue that I came across when
> compiling the native gems on the remote machine: does module do_mysql
> compile with mysql 4.1 libraries?
>

See this posting on the DataMapper list:
http://groups.google.com/group/datamapper/msg/70d9d1d662ab1879

4.1 isn't officially supported, but you can try applying Dirkjan's
patch and see if it works for you (it would be helpful for the project
if you can report back if it works or not!).

Alex

[Mr_Tibs]

Thanks Yehuda.

On Feb 27, 6:16 pm, Yehuda Katz <wyc...@gmail.com> wrote:
> You need ruby, rubygems, and thor on the remote machine.
>
> -- Yehuda
>

> 2009/2/27 Mr_Tibs <tiberiu.mo...@gmail.com>

[Mr_Tibs]

Hi Alex,

Thanks so much! I've applied the patch, repackaged the do_mysql gem
and it did build the native extensions on the machine with the 4.1
mysql libraries. I haven't tested the functionality yet. I'll try it
tomorrow.

Thanks again,
Tiberiu Motoc

On Feb 28, 3:53 am, Alex Coles <alex.co...@gmail.com> wrote:

[Mr_Tibs]

My excitement died a few minutes ago. That patch is enough for
compilation, but you get many runtime errors. It started with the
migrations task complaining about some sql modes which do not exist in
4.1 (in do_mysql_ext.c). I fixed those, then I got errors while trying
to access the "information_schema" table - another mysql 5 feature. I
grep-ed "information_schema" and it is used in at least 3 modules. It
is easier for me to migrate to mysql 5 than to figure out what needs
to be patched.

Tiberiu :(