Comment # 9 on bug 1050715 from Frank Kruger

(In reply to Wolfgang Bauer from comment #8)
> (In reply to Frank Kruger from comment #6)
> > cdrskin is a limited cdrecord compatibility wrapper, so I would stick to
> > cdrecord. Is there any good reason against it?
> 
> Against sticking to cdrecord?
> Not that I know, except that mentioned message on k3b's startup...
> 
> AFAIK the cdrskin developer helped with implementing the support in k3b
> though (and fix other bugs), maybe that's the reason why it would be
> preferred now.

k3b with cdrecord just works for me for years, so why should I switch to
cdrskin? I do not see any improvment in using cdrskin.