Wed 07 Mar 2007 04:18:59 AM UTC, comment #4:
The changes are not a reflection on the usefulness of the feature, but more the reality that it doesn't fall within the confines of the project, even if there were someone in libcdio to do it.
However, using what is currently in the library, I believe this can be done completely outside as a user application much as uniject or samba-vfs are.
(Well, almost. There will probably be bugs discovered in libcdio as a result of such an understaking, but that's different matter.)
For myself, those projects that I really want to get done I will take a more active role. Were I to rely on feature requests, libcdio would not have gotten written. (Nor would there have been bash and make debuggers, etc.)
A comment I often hear when I suggest something along these lines is: "Gee, I'm not a programmer, and/or I don't know/care all that much about [fill in the blank]. I sympathize. Because before undertaking libcdio, I too felt exactly this way.
Finally, there are many ways to take a more active role. One way is to write the program. In this case I think any reasonably competent programmer could do it if they had the desire and willingness to spend time.
But let's say all of those several people that think this is a good idea truly aren't programmers and will never become programmers. Okay, then maybe the collective you could hire a programmer to write it.
Finally, one can wishfully hope that Google or some benevolent organization will get it done on your behalf. But that's not a good bet either. Last year there were no serious college-student programmers interested in working on libcdio.
If wishes were pennies, I'd be a millionaire.
|