[Ogden] Ogden Rakefile patch

[Mark Van De Vyver]

Hi
Attached is a Rakefile patch, essentially I edited the Sequel Rakefile...

I placed two TODO items, but there maybe more - I've never worked with
rubyforge and gems.

The spec/*_spec.rb convention is assumed.

Let me know if I should change how a patch is submitted.

HTH

[Trans]

Since this is the second Rakefile suggestion. I'll go ahead and put a
complete build system in place.

T.
_______________________________________________
Ogden-developers mailing list
Ogden-de...@rubyforge.org
http://rubyforge.org/mailman/listinfo/ogden-developers

[Judson Lester]

On Dec 20, 2007 4:58 AM, Trans <tran...@gmail.com> wrote:

Since this is the second Rakefile suggestion. I'll go ahead and put a
complete build system in place.

If you mean ratch by that, could you talk for a moment about the benefits of ratch over rake?

Judson
--
Your subnet is currently 169.254.0.0/16.  You are likely to be eaten by a grue.

[Trans]

On Dec 20, 2:13 pm, "Judson Lester" <nya...@gmail.com> wrote:

> On Dec 20, 2007 4:58 AM, Trans <transf...@gmail.com> wrote:
>
> > Since this is the second Rakefile suggestion. I'll go ahead and put a
> > complete build system in place.
>
> > If you mean ratch by that, could you talk for a moment about the benefits
>
> of ratch over rake?

Better and easier to use ;-)

No, seriously. Rake is a good system and has certain advantages. It's
more mature for instance. But I've designed Ratch as sort of "Next
Generation" with a string focus on ease of use and "unix-way"
thinking. The main distinction is that Ratch uses script files rather
than a monolithic system. This make it easy to isolate particular
needs. Yet, these scripts can reference each other as needed, and each
can define sub-tasks and builds. Evn more important though, the DSL
Ratch provides is much more extensive.

I'm still working on docs, so until that's further along the best
thing is for me to show you. If you look in the current trunk of Ogden
you will see a task/ directory. This is where all the ratch scripts
reside. Most of these scripts are simply copies from ratch's toolset
repository and are fully general purpose, ready to go with only a
little configuration via meta/config.yaml.

I need to finish tweaking a few tasks though, and a few other's I
still need to add. But I think there's enough there to get the idea.

Ratch itself is ~90%, I'd say. There's still one major design question
I have to consider, and one other major feature I know I need to add.
No doubt there will be a few other details yet, but I'm confident
enough in the system and I have been using it for a few months on all
my other project quite happily. In a few more months I should think
I'd be ready to recommend it to the community at large.