On Mon, Jan 5, 2009 at 3:28 PM, Daniel Spiewak <[email protected]> wrote:
> Incidentally, should we make tasks like `shell:jirb` project-local, or just
> `shell`?
I think for most builds you only need one shell, so a per-buildfile
shell is easier to work with, configure, etc.
I know scenarios where I would like to (or have and so use) multiple
shells, but those are task-based not project-based. For example, when
working with Rails, I use the server console, database console
(embedded sqlite), and bash/irb for the client.
So it would be nice if I could easy define new shells from the buildfile, say:
ShellTask.define_task('client').with( lots of dependencies )
Assaf
>
> Daniel
>
> On Mon, Jan 5, 2009 at 5:00 PM, Alex Boisvert <[email protected]> wrote:
>
>> On Mon, Jan 5, 2009 at 2:55 PM, Daniel Spiewak <[email protected]>
>> wrote:
>>
>> > Assaf's parametrized idea seems like the "proper" way to do this, but I
>> > don't like the syntax. At least to my eye, shell:jirb is *much* nicer
>> and
>> > more consistent with the "Buildr philosphy" than shell[jirb]. Besides,
>> the
>> > former is marginally easier to type.
>>
>>
>> I feel the same way. I'm curious to see if many Rake-based projects will
>> adopt this new convention.
>>
>>
>> > We could use your multiple-tasks idea without too much hardship in the
>> > implementation. I've got all the providers in a Hash, so a simple .each
>> {
>> > |lang, prov| define_task ... } should be sufficient. I'm fine with doing
>> > it
>> > this way as long as y'all are ok with it. :-)
>>
>>
>> One precedent I can think of is the form "buildr test:SomeTest", which I
>> like so I'm supportive of following our existing convention.
>>
>> alex
>>
>
