chroot is not really the same thing... ie it's not really a standard
or normal way of having Rake tasks globally available... ie I can't
use it that way regularly.
Rakefile in / does work i guess, but makes me think when i said
'globally available' i really meant 'per-user'.
Still no comment from the great and benevolent leader Jim... ;)
-Adam
On 19/06/2008, at 7:22 PM, James Tucker wrote:
chroot to ~, or put Rakefile in / also works...
As much as I'd like sake with less overhead, i think this already
works in some fashion, except for across drives on win32.
On 19 Jun 2008, at 10:01, Adam Salter wrote:
Hey all,
Just wanted to run this by the list....
Is anybody adverse to me implementing basic 'sake' functionality?
sake is a system-wide rake, and basically just reads the rake tasks
from ~/.sake (ok - it does a fair bit more - sorry Chris for
denegrating your good work! ;)
I suggest having a (optional) ~/.rake which is only read if no
other rake file is found (or a command line option is added).
This means you could have rake tasks for general stuff.
E.g.
rake system:clean_temp_files
Sake implements a lot of other functionality, reading tasks from
websites, internal server for serving tasks, but the basic
functionality could be a good fit for pulling into rake.
Want to run this by the list before I get started, so I don't
implement and find that it's rejected.
Best,
-Adam
_______________________________________________
Rake-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rake-devel
_______________________________________________
Rake-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rake-devel
_______________________________________________
Rake-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rake-devel
