app-cdr/cdrecord-prodvd depends on app-cdr/cdrtools but should depend on virtual/cdrtools. - There are no conflicting names/files - If virtual/cdrtools is dvdrtools, the user is free to compare and is able to use the "other" tool in worst case Reproducible: Always Steps to Reproduce:
I don't think that this is a good idea. cdrecord-prodvd is built an maintained by the same author of cdrtools. These tools should work in combination. dvdrtools is a quite early fork of cdrtools (version 1.11). ATAPI-support has been backported lately to it. I can't test the combination dvdrtools/cdrecord-prodvd on my own, as the cdrecord-prodvd-binaries are not shipped for my platform. But, what does dvdrtools provide what cdrecord/cdrecord-prodvd can't provide? The user should choose one combination, that fit his needs. And currently everything than dvdrtools looks better. I had some nasty problems with it (but that is another bug...).
This is a matter of freedom of choice. Ok, will make appropriate test, then re-open