Jerry: >> Wouldn't it be better to make the two >> configurable. It would be better to specify, when running the configure >> script which backend to use. Then the code should just use #ifdef's so >> the right backend code is executed. > Cdrdao has't been updated for 2 years. Its last update happened on 2006. > Since then, development for cdrdao is dead. So I think it make more > sense to replace it with more popular and active cdrecord & cdda2wav.
I can appreciate that you want to encourage distros to switch to the more maintained projects. However, some distros may not be able to easily or quickly switch. Therefore, I'd think that making it possible to configure this via configure would make the patch more likely to go upstream. To just switch from one CD backend to another might cause too much trouble for some distros. >> Then, I'd think this patch could go upstream, and we could just call >> configure with the right options to build the code as we need. No? > I'm trying to persuade the community maintainer to accept this patch. > For the detailed info, please see bugzilla bug#550966. Yes, I would continue working with the maintainer on this. However, it wouldn't surprise me if he would insist that the old support not just disappear. Most maintainers require a degree of backwards compatibility. Brian
