Fabien,
Can you point to me the part of the thor code I need to start to debug
this?
I guess I just don't understand.  I thought the thor tasks pulled the
source, then staged the gem build, then called gem to install.
Since gem automatically installs to ~/.gem if it doesn't have write
privileges to the system directories, you just let gem do its thing.
How does running from the thor tasks change this default gem install
behavior?  There should be no reason to hard code into thor where gem
installs.  That behavior belongs to gem and its environment config.

I'm happy to look at the source and try to fix the problem.  Can you
give me a pointer on where to start looking?
With sooo many gems for a full merb install, uninstall each one by
hand is a serious pain.
By having everything under ~/.gem, I can very easily drop the entire
structure and reinstall.  I can't do this with a system-wide install
as I can't track which files went into /usr/bin
I do understand gems is not the most robust solution, which is why I
like to install local.

thanks,  Jon


On Oct 15, 7:50 pm, loob2 <[EMAIL PROTECTED]> wrote:
> Jon,
>
> I was being serious, mind you. And I still consider this an edge case
> for the people we cater for with merb.thor. Advanced users like
> yourself shouldn't have a problem with managing their stack installs
> themselves: it's just a 'gem install merb' away afterall (especially
> since you're after stable gems in this case).
>
> If you really need this functionality, why not contribute like many
> people already have?
>
> To be honest, I seriously took your issue into consideration and
> tested some ways to provide what you need. But adding another option
> accross all tasks (since most of them us this) wasn't the way to go,
> since we want to keep merb.thor clear and simple. If you insist, we
> could probably add it using an ENV flag like ENV['USER_INSTALL_GEMS']
> or so, but that'd be hidden from regular users.
>
> - Fabien
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"merb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/merb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to