[Rake-devel] Rakefile optional when using a rake directory
assaf at labnotes.org
Wed Feb 27 12:57:20 EST 2008
On Tue, Feb 26, 2008 at 4:04 AM, Adam Salter <adam.q.salter at gmail.com> wrote:
> I suspect you understand the actual tone with which my comment was
> expressed (albeit a little hurriedly)...
> Of course it's good to make a request. But it's only a request. A
> request and a patch is better.
I beg to differ.
If you need something, ask for it. There's a high chance that it
already exists just not apparent to you, someone else is working on it
or motivated to make it happen by your request, that it was attempted
before but didn't work, doesn't fit the goals of the project, or that
there's a better way of doing things. Asking costs nothing, and you
get more people involved in figuring out the solution.
The only rule is, don't expect anything to happen without putting
effort into it. The effort to make a code change happens involves a
patch, but the right way to start is often enough to ask first.
> Generally in the "open source" world it is necessary to be "the change
> you want to see". In other words if you really want to see something
> done do it yourself. Submit a patch, _and_ discuss/request. We are all
> busy people and I'm sure the principle maintainer, Jim, has his own
> things to think about.
> As it happens Transfire was quick to supply a patch of sorts, but I'm
> not sure I like loading all files in a directory as rakefiles or
> running without an explicit rakefile.
> There is sake if you need it (http://errtheblog.com/posts/60-sake-bomb).
> And Transfire could always patch his own version (or even fork rake)
> if he really wants his functionality.
> On 26/02/2008, at 12:09 AM, Hugh Sasse wrote:
> > On Sun, 24 Feb 2008, Adam Salter wrote:
> >> Ummm, a suggestion without a patch is pretty useless.
> > Are you saying that discussing an idea with people who know the
> > project inside out, who could tell you whether another approach
> > would meet your needs (better, perhaps), who could save you writing
> > and debugging code, and who could save themselves having to read it
> > would be a waste of time? Are you saying that you should not
> > contribute ideas to one project if your commitments to contribute
> > code for other projects means you have no available time?
> > Hugh
> > _______________________________________________
> > Rake-devel mailing list
> > Rake-devel at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rake-devel
> Rake-devel mailing list
> Rake-devel at rubyforge.org
More information about the Rake-devel