[PATCH] Make Ruby path configurable

Hi,

I've made a small patch that allows you to specify Ruby path which is
used when executing tests. I needed it to use rcov (code coverage
tool) with Rake in my Rails appilcation.
With this patch, you can run rcov with your test using the following
command line:

rake test_units RUBY=rcov

Note that this doesn't work when warning is set to true, because rcov
doesn't recognize "-w" option.

I found this article describing how to use rcov with Rake, but rather
than adding Rake tasks, I thought it would be smarter if Rake had an
option to specify Ruby path.

http://asplake.blogspot.com/2006/01/test-coverage-with-rcov-and-rake-962.html

I tried to write unit test for this patch, but I gave up...

Thanks,
Shinya

_______________________________________________
Rake-devel mailing list
Rake-devel <at> rubyforge.org
http://rubyforge.org/mailman/listinfo/rake-devel

[PATCH] rake --directory option

This simple patch adds the --directory option that allows to change the
execution directory for rake.

thanks.
--

-- 
vic

_______________________________________________
Rake-devel mailing list
Rake-devel <at> rubyforge.org
http://rubyforge.org/mailman/listinfo/rake-devel

Package tasks

Hi all,

I'm using Rake to build packages for a few different projects of mine[1],
and I'm finding that the package task as not really set up to go well with
how packages really work.

In particuar, it makes no mention of binary directory, library directories,
man page directories, or any of the standard file locations.  Would there be
any interest in a reworked package task that used the rbconfig variables and
required that users specify binaries, libraries, etc, storing them
accordingly?

I plan to use EPM[2] to do most of my package building, so I should be
able to contribute that, also.

Lastly, is anyone using rake to manage multiple projects?  I've listed four
projects below, but I'm adding projects all of the time, and I'm wondering
if people have any helpful hints in this process.  Obviously, part of it is
creating common tasks and putting them into a common library, but do people
create a separate "build" repository, or what?

Thanks,
Luke

1 -- http://reductivelabs.com/projects/puppet
     http://reductivelabs.com/projects/facter
     http://reductivelabs.com/projects/enhos
     http://reductivelabs.com/projects/naginator

2 -- http://www.easysw.com/epm/

Rake best practices for managing multi-directory project...

Hi,

Apologies for sending a Rake usage message to this list but
I figure it's the best way to reach experienced Rake users
too.

I'm currently working on a project with a number of "modules"
in different directories.  I'm using Rake to manage the running
of the module services in the correct order.

I have a directory structure something like this:

       /project
          +-- Rakefile

          +-- module A
                +-- module A files
                +-- tasks.rake

          +-- module B
                +-- module B files
                + tasks.rake

          +-- module C
                etc

So each module directory has its own tasks.rake file and all
the SQL, shell, Ruby etc scripts needed to implement the
service it provides.  Each tasks.rake uses Rake namespaces
fully to avoid any task name ambiguity across the project.

Re: Package tasks

Luke Kanies [2006-03-13 16:05]:
> I'm using Rake to build packages for a few different projects of mine[1],
> and I'm finding that the package task as not really set up to go well with
> how packages really work.
> 
> In particuar, it makes no mention of binary directory, library directories,
> man page directories, or any of the standard file locations.  Would there be
> any interest in a reworked package task that used the rbconfig variables and
> required that users specify binaries, libraries, etc, storing them
> accordingly?

I think you don't understand what Rake's PackageTask is supposed to do.

It's supposed to build a tarball/zip archive that contains stuff in your
source tree. So it doesn't need to know where the system stores
libraries or man pages...

Regards,
Tilman

--

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

_______________________________________________
Rake-devel mailing list
Rake-devel <at> rubyforge.org

[PATCH] safe_ln

Hi,

Am using ruby 1.8.4 on WinXP through the OneClick installer (RC 1
build). I came across an issue with Rake's PackageTask using safe_ln.
It appear that ln now throws a NotImplemented error on Windows, rather
than an Errno. This fixes it:

--- rake.rb     2006-03-31 10:21:13.439299300 +1100
+++ rake.rb.patched     2006-03-31 10:19:15.482491100 +1100
 <at>  <at>  -603,7 +603,7  <at>  <at> 
     else
       begin
         ln(*args)
-      rescue Errno::EOPNOTSUPP, Errno::EXDEV
+      rescue Errno::EOPNOTSUPP, Errno::EXDEV, NotImplementedError
         LN_SUPPORTED[0] = false
         cp(*args)
       end

I haven't done a full scale investigation, I just saw the error and
the fix seems obvious and trivial. If you need me to carry out more
tests just let me know.

Cheers,
Assaph