rpa update

[Peña, Botp]

I just ran rpa update

---------------------------------
c:\family\ruby>rpa update
Getting port info from http://rpa-base.rubyforge.org/ports/ports.info.
100% [========================================] 79727 bytes

Ports added since Tue, 24 Aug 2004 16:22:41 +0800:
archive-tar-minitar 0.5.0-1 Library and command-line utility to deal
with
bz2 0.2.1-1 Extension to use libbzip2 from Ruby.

Ports updated since Tue, 24 Aug 2004 16:22:41 +0800:
actionpack 0.8.0-1 -> 0.8.5-1
activerecord 0.9.4-1 -> 0.9.5-1
rpa-base 0.2.1-7 -> 0.2.1-8
---------------------------------



And I noticed that rpa-base was also updated. It would be small good idea to
put a notice on last line perhaps that rpa-base was updated... like

Ports updated since Tue, 24 Aug 2004 16:22:41 +0800:
actionpack 0.8.0-1 -> 0.8.5-1
activerecord 0.9.4-1 -> 0.9.5-1
rpa-base 0.2.1-7 -> 0.2.1-8

"rpa-base was updated pls run rpa install rpa-base now"...


Or perhaps, rpa update also runs rpa install rpa-base if rpa-base if
updated?


Just some small thoughts..
Thank you for rpa.

kind regards -botp

 

[Mauricio Fernández]

And I noticed that rpa-base was also updated. It would be small good idea to
put a notice on last line perhaps that rpa-base was updated... like

Ports updated since Tue, 24 Aug 2004 16:22:41 +0800:
actionpack 0.8.0-1 -> 0.8.5-1
activerecord 0.9.4-1 -> 0.9.5-1
rpa-base 0.2.1-7 -> 0.2.1-8

"rpa-base was updated pls run rpa install rpa-base now"...


Or perhaps, rpa update also runs rpa install rpa-base if rpa-base if
updated?

mmm sounds good. The only problem is that since this will make everybody
use the latest version always, I'll really have to make sure that rpa-base
isn't broken and can still update itself, etc

IIRC such a problem happened once, around 0.2.0-28 or maybe 0.2.1-1, where
rpa-base wouldn't install itself correctly when using a non-standard
$prefix. I fixed it quickly and AFAIK nobody was bitten. Anyway, in
the worst possible case, you'd just have to install rpa-base from the
tar.gz again (it would adopt the installed ports, etc). Not quite as
convenient as a simple rpa install rpa-base but still acceptable.
And this won't be a problem when I make rpa install rpa-base itself
atomic.

 

[Mauricio Fernández]

And I noticed that rpa-base was also updated. It would be small good idea to
put a notice on last line perhaps that rpa-base was updated... like

Ports updated since Tue, 24 Aug 2004 16:22:41 +0800:
actionpack 0.8.0-1 -> 0.8.5-1
activerecord 0.9.4-1 -> 0.9.5-1
rpa-base 0.2.1-7 -> 0.2.1-8

"rpa-base was updated pls run rpa install rpa-base now"...


Or perhaps, rpa update also runs rpa install rpa-base if rpa-base if
updated?

(note: I'm cheating a tiny bit, since it would normally happen only
*after* 0.2.1-9, which is the 1st version with auto self-update; I just
installed 0.2.1-9 directly with ruby install.rb before doing the rpa
update -- that's why it says it's unchanged)

batsman@tux-chan:~/src/rpa/rpa-base$ rpa update --no-proxy
Getting port info from http://rpa-base.rubyforge.org/ports/ports.info.
100% [========================================] 79781 bytes

Ports updated since the last update (in the last 14 days):
rpa-base 0.2.1-8 -> 0.2.1-9


** New version of rpa-base available, will install it. **

Installing ports
Getting port rpa-base from http://rpa-base.rubyforge.org/ports/rpa-base_0.2.1-9.rps.
100% [========================================] 58880 bytes
Defaults loaded...
Recovering defaults...
Building rpa-base (0.2.1-9).
Fixed shebang in rpa/tmp/bin/rpa-buildrepos.rb.
Fixed shebang in rpa/tmp/bin/rpaadmin.
Fixed shebang in rpa/tmp/bin/rpa-buildport.
Fixed shebang in rpa/tmp/bin/rpa.
Calculating MD5 digests.
Building package in rpa-base_0.2.1-9_i686-pc-linux-gnu.rpa.
Installing rpa-base
Reusing cached package /home/batsman/usr/lib/ruby/rpa0.0/packages/rpa-base_0.2.1-9_i686-pc-linux-gnu.rpa.
Package rpa-base unchanged.
Starting lightweight (metadata only) transaction for rpa-base
Finished lightweight (metadata only) transaction for rpa-base
Committed changes