On Jul 12, 3:29 pm, Charlie Savage <[EMAIL PROTECTED]> wrote:
> Looking into the setup.rb issues, I realized two things:
>
> * setup.rb wasn't included in the gems or .tgz packages, that is now fixed
>
> * setup.rb was using an unreleased 3.5.0 version
>
> The problem with the second issue is when I tried to run setup.rb on
> Linux (Fedora 8), it didn't work. The offending line was line 10 at the
> very start:
>
> PACKAGE = File.read(Dir.glob('{.,meta/}unixname{,.txt}',
>
> So, I reverted to the last official setup.rb release, 3.4.1. That one
> ran correctly when I tried using it.
>
> As a result, I've checked in the older version. Feel free to shout out
> if this is the wrong thing to do.
Well, I'd like to know why the line wasn't working? The line was there
in order to support installation of documentation to standard OS
location --a 3.5.0 feature. If the line had a problem finding the
file my guess is the package was also missing the meta/ directory.
Ultimately this line isn't the best solution, but it sufficed until a
better approach became apparent. That aside, a quick fix would have
been:
PACKAGE = 'libxml-ruby'
which is all this effectively does.
I realize that there is a great energy moving things along right now.
Believe me, I more than anyone am happy to see it! But I have to ask
you to consider a bit more why things may be the way they are. If
you're not sure then ask. For instance, I just rechecked out the
current trunk, and I see that lib/libxml has been moved to to just
lib/. That will break things very badly for anyone who installs using
setup.rb --in fact it will make a mess of their site_ruby directory!
Please move it back.
You can leave the 3.4.1 version of setup.rb for now. That's fine.
3.5.0 still needed a few tweaks --and as I said before I'd like to
replace it altogether anyway.
T.
_______________________________________________
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel
