# Deconflicting namespaces

**URL:** <https://www.ruby-forum.com/t/deconflicting-namespaces/133189>\
**Category:** Rails\
**Created:** [March 28, 2008, 4:24pm UTC](https://www.ruby-forum.com/t/deconflicting-namespaces/133189 "2008-03-28T16:24:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![avramd](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/aca169/32.png) [@avramd](https://www.ruby-forum.com/u/avramd)\
**Post date:** [March 28, 2008, 4:24pm UTC](https://www.ruby-forum.com/t/deconflicting-namespaces/133189/1 "2008-03-28T16:24:25Z")

</div>

Hello,

I’m in the unfortunate position of needing to include a gem whose name  
conflict with an existing class in my application. Specifically, I  
already have a Color class, and I’m trying to add the Color (v1.4)  
gem. Obviously these namespaces conflict.

Is there some magical way that I can wrap the Color gem in another  
namespace when I require it, so that instead of just Color::\* it  
becomes External::Color::\*?

Going through all my code and changing the name of my Color class is  
turning out to be not only painful, but probably highly error prone.

Thanks,  
AVram