Bug and one last suggestion for setup.rb

T

trans. (T. Onoma)

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.
 
T

trans. (T. Onoma)

This Bug given below, was worse then I thought. It actually created all those
lib directories!

T.

On Tuesday 26 October 2004 02:05 pm, trans. (T. Onoma) wrote:
| 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/l
|ib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/lib/a
|bc/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.

--
( o _ カラãƒ
// trans.
/ \ (e-mail address removed)

I don't give a damn for a man that can only spell a word one way.
-Mark Twain
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Syntax error, want to use multiple variables in one line, copy mysqldata 1
ModuleNotFoundError: No module named 'pyaudio' on Mac (with Anaconda installed) 0
Rails: Problem with test-environment and mysql2 database 3
setup.rb --prefix not working? 0
Problems with 'gem require' and test-unit gem 2
rubygem setup.rb failing 2
Ugly bug with one-click installer and postgres-pr 1
Execute environment - rake aborted! - no such file to load -- openssl 0

Members online

Total: 24 (members: 1, guests: 23)
Robots: 450

Forum statistics

Threads
473,770
Messages
2,569,583
Members
45,075
Latest member
MakersCBDBloodSupport

Latest Threads

Top