Greetings, I’m pleased to announce the release of Log4r 1.0.5. The
notable thing about this release is that Log4r is now available as a gem,
allowing for dead simple installs. No need to squint at a cramped
SourceForge release page!
gem --remote-install=log4r
And for the less hip:
Download: http://sourceforge.net/project/showfiles.php?group_id=43396
New stuff:
o Configure log4r with YAML (instead of finger-cramping XML) (Andreas Hund)
o Syslog binding now uses full range of syslog error levels
o Log4r gem available via RubyGems
o Last release on SourceForge, moving to RubyForge!
Let me know if this build barfs. I can’t test on a wide range of setups.
Leon Torres
"Log4r ate my day."
thanks, it’s wonderful to see that you’re still working on it 
···
il Thu, 18 Mar 2004 18:05:53 +0900, Leon Torres leon@ugcs.caltech.edu ha scritto::
Greetings, I’m pleased to announce the release of Log4r 1.0.5. The
notable thing about this release is that Log4r is now available as a gem,
allowing for dead simple installs. No need to squint at a cramped
$ gem --remote-install log4r
Error installing gem log4r: Could not find log4r > 0.0.0 in the repository
Probably my problem. Anyone know how to fix it?
Gavin
PS.
$ gem --remote-list
anothertest-1.2.3 - This is a test spec
anothertest-3.2 - This is a test spec
chad-1.2.3 - This is a test spec
chad-2.4 - This is another test spec
sources-0.0.1 - This package provides download sources for remote gem installation
test-1.2.3 - This is a test spec
xmlparser-0.6.5 - Ruby wrapper for Expat XML Parser from James Clark
···
On Thursday, March 18, 2004, 8:05:53 PM, Leon wrote:
Greetings, I’m pleased to announce the release of Log4r 1.0.5. The
notable thing about this release is that Log4r is now available as a gem,
allowing for dead simple installs. No need to squint at a cramped
SourceForge release page!
gem --remote-install=log4r
C:\Documents and Settings\gabriele\Desktop\xml>gem
–remote-install=log4r
Successfully installed log4r version 1.0.5
er… I’d like to say to you the version of gem I’m running but I don’t
know how 
(it’s not the latest, but the previous one).
Ona sidenote: why does not exist a gem for rubygem itself?
···
il Thu, 18 Mar 2004 20:15:29 +0900, Gavin Sinclair gsinclair@soyabean.com.au ha scritto::
On Thursday, March 18, 2004, 8:05:53 PM, Leon wrote:
Greetings, I’m pleased to announce the release of Log4r 1.0.5. The
notable thing about this release is that Log4r is now available as a gem,
allowing for dead simple installs. No need to squint at a cramped
SourceForge release page!
gem --remote-install=log4r
$ gem --remote-install log4r
Error installing gem log4r: Could not find log4r > 0.0.0 in the repository
Probably my problem. Anyone know how to fix it?
The problem is that my RubyGems believes it should look towards
http://www.chadfowler.com:8808 to find remote gems, whereas the real
repository is now http://gems.rubyforge.org.
So how does RubyGems know where to look? It uses the (poorly named)
“sources” gem, whose sole purpose is to define Gem.sources.
My local copy of “sources” is at version 0.0.1. The version on
chadfowler.com is also version 0.0.1. “sources” doesn’t exist at
gems.rubyforge.org, so I can’t get a new copy from there.
So I’ll manually hack it (the installed gem, that is and see how I
go.
Yep. Setting it to “http://gems.rubyforge.org” did the trick. I can
now see a proper remote list.
So how does a fresh installation of RubyGems know where to look? I’m
running latest CVS.
Cheers,
Gavin
···
On Thursday, March 18, 2004, 10:15:29 PM, Gavin wrote:
On Thursday, March 18, 2004, 8:05:53 PM, Leon wrote:
Greetings, I’m pleased to announce the release of Log4r 1.0.5. The
notable thing about this release is that Log4r is now available as a gem,
allowing for dead simple installs. No need to squint at a cramped
SourceForge release page!
gem --remote-install=log4r
$ gem --remote-install log4r
Error installing gem log4r: Could not find log4r > 0.0.0 in the repository
Probably my problem. Anyone know how to fix it?
Greetings, I’m pleased to announce the release of Log4r 1.0.5. The
notable thing about this release is that Log4r is now available as a
gem,
allowing for dead simple installs. No need to squint at a cramped
SourceForge release page!
gem --remote-install=log4r
$ gem --remote-install log4r
Error installing gem log4r: Could not find log4r > 0.0.0 in the
repository
Probably my problem. Anyone know how to fix it?
Gavin
PS.
It looks like you have an old sources file from before the alpha
release. If you look in the sources gem in your gem directory, you
should see “lib/sources.rb”. My guess is that you’re going to find a
reference to http://www.chadfowler.com in there, which will point to a
webrick server running on my machine. The easiest thing to do would be
to run RubyGems’ install.rb again, though if all you want to do is
update your sources, you can find the gemspec for the sources package
in #{rubygemsdistrodir}/packages/sources, from which you can generate a
gem and install it.
Chad
···
On Mar 18, 2004, at 6:15 AM, Gavin Sinclair wrote:
On Thursday, March 18, 2004, 8:05:53 PM, Leon wrote:
$ gem --remote-list
anothertest-1.2.3 - This is a test spec
anothertest-3.2 - This is a test spec
chad-1.2.3 - This is a test spec
chad-2.4 - This is another test spec
sources-0.0.1 - This package provides download sources for remote gem
installation
test-1.2.3 - This is a test spec
xmlparser-0.6.5 - Ruby wrapper for Expat XML Parser from James Clark
Thanks! Spending time with Ruby actually cures the programming blues.
···
On Thu, Mar 18, 2004 at 06:54:32PM +0900, gabriele renzi wrote:
thanks, it’s wonderful to see that you’re still working on it
Greetings, I’m pleased to announce the release of Log4r 1.0.5. The
notable thing about this release is that Log4r is now available as a
gem,
allowing for dead simple installs. No need to squint at a cramped
SourceForge release page!
gem --remote-install=log4r
$ gem --remote-install log4r
Error installing gem log4r: Could not find log4r > 0.0.0 in the
repository
Probably my problem. Anyone know how to fix it?
C:\Documents and Settings\gabriele\Desktop\xml>gem
–remote-install=log4r
Successfully installed log4r version 1.0.5
er… I’d like to say to you the version of gem I’m running but I don’t
know how (it’s not the latest, but the previous one).
Do you mean you want to say the version of the RubyGems package or the
gem itself? You can see from installation that it’s 1.0.5 or you could
do “gem --list” to see all of the gems and versions that are installed.
The CVS version of RubyGems has both --search and --remote-search
options now, so you can display info for a specific gem you have
installed.
Ona sidenote: why does not exist a gem for rubygem itself?
We did put the sources package into a gem. We’ll probably look at
doing that with more of the pieces of RubyGems in the future. It would
certainly make upgrading easier.
Chad
···
On Mar 18, 2004, at 7:09 AM, gabriele renzi wrote:
il Thu, 18 Mar 2004 20:15:29 +0900, Gavin Sinclair > gsinclair@soyabean.com.au ha scritto::
On Thursday, March 18, 2004, 8:05:53 PM, Leon wrote:
Greetings, I’m pleased to announce the release of Log4r 1.0.5. The
notable thing about this release is that Log4r is now available as a
gem,
allowing for dead simple installs. No need to squint at a cramped
SourceForge release page!
gem --remote-install=log4r
$ gem --remote-install log4r
Error installing gem log4r: Could not find log4r > 0.0.0 in the
repository
Probably my problem. Anyone know how to fix it?
The problem is that my RubyGems believes it should look towards
http://www.chadfowler.com:8808 to find remote gems, whereas the real
repository is now http://gems.rubyforge.org.
So how does RubyGems know where to look? It uses the (poorly named)
“sources” gem, whose sole purpose is to define Gem.sources.
The name is familiar to people who use debian or other apt-based
systems. Gems is loosely modeled after Debian’s apt (among other
packaging systems). So, “sources” isn’t probably as poorly named as
you think. The point of this being a gem, obviously, is that it
can be updated remotely.
My local copy of “sources” is at version 0.0.1. The version on
chadfowler.com is also version 0.0.1. “sources” doesn’t exist at
gems.rubyforge.org, so I can’t get a new copy from there.
The idea is definitely that we could update it remotely at some point.
For now, RubyGems Alpha ships with the most recent sources package (as
does RubyGems CVS).
So I’ll manually hack it (the installed gem, that is and see how I
go.
Yep. Setting it to “http://gems.rubyforge.org” did the trick. I can
now see a proper remote list.
So how does a fresh installation of RubyGems know where to look? I’m
running latest CVS.
Looks like you may be having some CVS update problems. Either that,
or install.rb didn’t work properly? On my box, if I change sources.rb
and re-run install.rb, I get the new sources gem installed.
···
On Mar 18, 2004, at 7:21 AM, Gavin Sinclair wrote:
On Thursday, March 18, 2004, 10:15:29 PM, Gavin wrote:
On Thursday, March 18, 2004, 8:05:53 PM, Leon wrote:
no, the version of RubyGems I’m using. I mean, obviously I can’t do a
gem -v or --version, but a
–rubygems-version would be useful, imo. (I finally found
RubyGemsVersion =‘1.0’, myabe this is the actual pkg version)
Another strange thins in the options is that
–help works as expected, while -h asks for a missing argument.
Looking at the gem executable it seem that there is no -h switch, how
this came out ?
PS
I just noticed tha the same happens for -r, -s and -v says it’s
ambiguos, so this may be just an automagical feature to use short
options for longer ones. But it’s undocumented, and confusing.
…
···
il Thu, 18 Mar 2004 21:26:55 +0900, Chad Fowler chad@chadfowler.com ha scritto::
On Mar 18, 2004, at 7:09 AM, gabriele renzi wrote:
er… I’d like to say to you the version of gem I’m running but I don’t
know how (it’s not the latest, but the previous one).
Do you mean you want to say the version of the RubyGems package or the
gem itself?
(it’s not the latest, but the previous one).