On Tue, Aug 10, 2004 at 07:48:54AM +0900, Joel VanderWerf wrote:
> >>This seems to happen for anything I try to install with rpa:
> >>
> >># rpa install ri-rpa
> >>Installing ports
> >>Getting port ri-rpa from 
> >>http://rpa-base.rubyforge.org/ports/ri-rpa_0.1-4.rps.
> >>100% [========================================] 264704 bytes
> >>Error: unrecognized arguments ri-rpa aborting

Could you try to run it with --debug, to get a backtrace?
Alternatively, you could try to put a debug statement in rpafrontend.rb around

    307         rescue => e
    308             $stderr.puts "Error: #{e} aborting"
    309             raise if @options.debug
    310             exit 6

(I think this is where the error is detected).

> Tried to run it in gdb to see where it was when exit() was called, but 
> running it in gdb "fixed" the problem:
> 
> This experience is repeated with other packages (I tried net-ssh):
> 
> What could be different about running in gdb? My normal shell is zsh, 
> but bash has the same effect.
> 
> Once a package is installed, doing "rpa install" on it again succeeds 
> (detecting no changes).

This makes me think it is somehow related to the ri/rdoc integration
and some shell quoting issue.

> RPA seems to work fine for me on windows, anyway.

That's good news at least, win32 was such a PITA to support from the
beginning ;-)

-- 
Running Debian GNU/Linux Sid (unstable)
batsman dot geo at yahoo dot com