From: "trans.  (T. Onoma)" <transami@...>
Date: 2004-10-27T03:05:28+09:00
Subject: Bug and one last suggestion for setup.rb

I have one last suggestion for setup.rb, which would make my desire for it to 
be "Rakeable" mute --there is also a bug (of-sorts) related to this.

Currently setup.rb can do multiple packages if you organize the packages 
according to a certain layout. One ends up with something like this:
 
  pkgname/
    setup.rb
    packages/
       pkgname-sub1/
         lib/
           pkgname-sub1/
         bin/
         ...
       pkgname-sub2/
         lib/
           pkgname-sub2/
         bin/
         ...

And so on. But this is really nothing more than saving one from multiple 
copies of setup.rb, while forcing you to have another layer in indirection. 
I'm inclined just to do this instead.

   pkgmain/
     pkgname-sub1/
       setup.rb
       lib/
         pkgname-sub1/
       bin/
       ...
     pkgname-sub2/
       setup.rb
       lib/
         pkgname-sub2/
       bin/
       ...

Another issue, and one the even is more problematic to me, is that I must be 
IN the same directory as setup.rb to run it. If you try to run it from 
another directory, say the lib directory or the test directory (b/c you 
running tests) like so:

  ruby ../setup.rb

Then you get pretty infinite loop output like so :(

<snip>
b/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/abc/symbol
---> 
lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/abc/numeric
<--- 
lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/abc/numeric
---> 
lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/abc/binding
<--- 
lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/abc/binding
---> 
lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/abc/integer
<--- 
lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/abc/integer
<--- 
lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/abc
---> 
lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/
</snip>

So I'd like to suggest that setup.rb be runnable from /usr/bin and need not be 
in the directory of the project, and instead it will look up the directory 
tree for a file called 'Setupfile' to know where the root is. This is how 
Rake works with Rakefile. The Setupfile could also be useful for setting 
parameters, including muti-package directories.

Thanks,
T.