On Fri, Jul 11, 2008 at 12:15 PM, Trans <[EMAIL PROTECTED]> wrote: > > > On Jul 11, 1:45 pm, "Aaron Patterson" <[EMAIL PROTECTED]> > wrote: > >> I've added a patch to the tracker that adds a test task and a build >> task to the rake file. >> >> http://rubyforge.org/tracker/index.php?func=detail&aid=21172&group_id... >> >> If you apply that patch, you can just execute 'rake build' to build >> the extension, and 'rake test' to run the tests. >> Also, 'rake extensions:clean' will clean up the extensions directory. > > It's important that setup.rb works and can do these things (i.e. > build, test, install, etc.) b/c that's is how people NOT using > RubyGems perform an installation. And since setup.rb already has to do > these things, it is not DRY to have separate code in the Rakefile to > do the exact same thing. This is why the original Rakefile loaded > setup.rb, which I had modified to support Rake tasks. So, if there is > a problem with using setup.rb we need to fix it, not just work around > it with a new rake task. > > However, I would like to do away with the setup.rb file and replace is > with a set of scripts in the directory "script/", eg. script/make, > script/test, script/install, etc. which (IMHO) is much more intuitive > way to provide these.
Separate scripts are more intuitive than rake tasks? -- Aaron Patterson http://tenderlovemaking.com/ _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
