Re: Drake: Distributed Rake
- From: "." <quixoticsycophant@xxxxxxxxx>
- Date: Tue, 9 Sep 2008 18:19:47 -0700 (PDT)
On Sep 9, 7:32 pm, Martin DeMello <martindeme...@xxxxxxxxx> wrote:
On Tue, Sep 9, 2008 at 4:13 PM, . <quixoticsycoph...@xxxxxxxxx> wrote:
(and I should hope we all agree), then there is nothing which can save
us. We are forced to write our Rakefiles correctly. No backwards
compatibility mode is possible for threads>1.
A --file-order-implies-dependency flag might get us there in a lot of
cases, though of course there's no general solution. Of more value
would be a lint tool that helps convert a rakefile into parallelisable
form.
martin
But I thought we just agreed those two forms should be the same? Now
you are proposing a flag which will make them different.
I think you're missing the larger point, which is that there are still
a million ways to make a mistake with the dependency graph. Your flag
will not come close to saving us.
A tool which analyzes our code and outputs what we meant to write
would be great. But until that glorious technology arrives, tools
will continue to operate on the principle of garbage-in, garbage-out.
As I've unsuccessfully explained in this thread, the problem lies in
our mistakes in thinking.
It seems to me the general solution is to not use -j until you've got
all your ducks in a row.
JL
.
- Follow-Ups:
- Re: Drake: Distributed Rake
- From: Martin DeMello
- Re: Drake: Distributed Rake
- References:
- [ANN] Drake: Distributed Rake
- From: quixoticsycophant
- Re: Drake: Distributed Rake
- From: Trans
- Re: Drake: Distributed Rake
- From: .
- Re: Drake: Distributed Rake
- From: Martin DeMello
- Re: Drake: Distributed Rake
- From: .
- Re: Drake: Distributed Rake
- From: Martin DeMello
- [ANN] Drake: Distributed Rake
- Prev by Date: Re: yield/block question
- Next by Date: Re: FileUtils.chdir thread safety
- Previous by thread: Re: Drake: Distributed Rake
- Next by thread: Re: Drake: Distributed Rake
- Index(es):
Relevant Pages
|