From: Dave Thomas <Dave@...>
Date: 2001-03-16T12:25:17+09:00
Subject: [ruby-talk:12708] Re: Library packaging

"Nathaniel Talbott" <ntalbott@rolemodelsoft.com> writes:

> The problem comes in when you want don't want to install Lapidary as
> a library, say to just look at it and run its internal unit
> tests. Suddenly, Lapidary doesn't work anymore, because it can't
> find itself! Aach! What to do? If it uses relative references, then
> it can't find its parts when run as a library; if it uses library
> references, then it can't find its parts when it's run standalone.

What happens if you organize your source files into directories that
mirror the final structure:

   ship:   site_ruby/Lapidary/a.rb
                             /support/b.rb
                             /support/c.rb

   devel:
           devel/Lapidary/a.rb
                         /support/b.rb
                         /support/c.rb


Then, to run in development you could just have
-I<path_to_devel/Lapidary>


Dave