However, if you download, and try to build with rake, you get:
bever:/usr/src/ruby/hpricot-0.4> rake
(in /home/source/src/ruby/hpricot-0.4)
rake aborted!
no such file to load -- rubygems
/home/source/src/ruby/hpricot-0.4/Rakefile:3:in `require'
(See full trace by running task with --trace)
So not preferring to use gems doesn't really buy you much.
Han Holl
PS I'm sending this to this list because Hpricot is not alone in this.
Dependencies on gem are not good. Of course I'll give in, install gem,
and subsequent dependencies will go unnoticed here, until I try to run
something on a different computer.
However, if you download, and try to build with rake, you get:
bever:/usr/src/ruby/hpricot-0.4> rake
(in /home/source/src/ruby/hpricot-0.4)
rake aborted!
no such file to load -- rubygems
/home/source/src/ruby/hpricot-0.4/Rakefile:3:in `require'
(See full trace by running task with --trace)
So not preferring to use gems doesn't really buy you much.
I think that most projects whose Rakefile depends on Gems do so because they need Gem::Specification for the Rake GemPackageTask. Generally I tend to leave out an explicit require and do something like:
require 'rubygems' rescue nil
# .... later:
if ! defined?(Gem)
warn "Package Target requires RubyGEMs"
else
spec = Gem::Specification.new do |s|
...
end
end
···
On Wed, 22 Nov 2006 12:38:13 -0000, Han Holl <han.holl@gmail.com> wrote:
However, if you download, and try to build with rake, you get:
bever:/usr/src/ruby/hpricot-0.4> rake
(in /home/source/src/ruby/hpricot-0.4)
rake aborted!
no such file to load -- rubygems
/home/source/src/ruby/hpricot-0.4/Rakefile:3:in `require'
(See full trace by running task with --trace)
So not preferring to use gems doesn't really buy you much.
Han Holl
PS I'm sending this to this list because Hpricot is not alone in this.
Dependencies on gem are not good. Of course I'll give in, install gem,
and subsequent dependencies will go unnoticed here, until I try to run
something on a different computer.
Thanks. It doesn't seem to be in SVN though, which is what I use.
It's no big deal, and I'm very enthioustastic about Hpricot.
Before this I experimented with htree, to_rexml and xpath, but this
combo was to slow to be workable.
The README file, by the way, ends rather abrubtly.
Han Holl
(Gmail seems to encourage top-posting, strange)
···
On 11/22/06, _why <why@ruby-lang.org> wrote:
Oh, I'm sorry, there should be a setup.rb in there. I've just updated the file
give it a try again. The installation commands is just `ruby setup.rb`.
Oops, I meant explicit dependency (in gems) rather than explicit require.
···
On Wed, 22 Nov 2006 13:12:05 -0000, Ross Bamford <rosco@roscopeco.remove.co.uk> wrote:
I think that most projects whose Rakefile depends on Gems do so because they need Gem::Specification for the Rake GemPackageTask. Generally I tend to leave out an explicit require and do something like: