"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> Matthias Andree wrote:
>> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
>> > Matthias Andree wrote:
>> >> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
>> >> > Why complicate the lives of cdrecord users with lots of options that
>> >> > don't even have a use case?
>> >>
>> >> Just because your view is limited and you cannot conceive a use case
>> >> (which is not bad in itself, just don't argue :-)), does not mean there
>> >> is none.
>> >
>> > Please explain the use case, otherwise we won't see it.
>>
>> The burden of proof is with you, you want the code to change in
> spite of
>> not being the maintainer.
Your mailer still breaks quotes. Please fix!
> Not just me, I'd say like 99% of cdrecord users.
I'd say 99.99% of cdrecord users are just taking what they're offered
for granted, and then start bitching if it doesn't work right. That's
much more of a threat than disagreeing with the upstream maintainer
about a default setting.
> Not hearing the users and [...] making software that doesn't help them
> is a real threat to free software that people like Jörg personify as
> the dictator of these projects (maybe he's paid by Micro$oft or some
> other people anti free software but I can't know)
Calm down. cdrecord is GPL'd, you're free to fork cdrecord today, create
your cdrecord-RJ-founded-community-version, add a statement that it's
Jörg's modified cdrecord, add your address as the address to send
complaints to. The GPL has the gory details.
>> You don't need to see the use case, but YOU need to PROVE the switch is
>> unneeded with every existing hardware before you can expect Jörg to even
>> consider removing it.
>
> So, what happens on those "broken" drives that support burnfree and
> you left burnfree on?
That is besides the point. You want the default to change, the
maintainer refuses, and if you want to convince him to still change the
default, you'll have to convince him that doing so is safe.
> Could cdrecord have workarounds for those drives like easy to use
> M$Windows CD recording software may have since they don't need the
> switch either and have burnfree turned on by default?
Read the code to find out. I'm sure you'll find more than just one
workaround which are already there.
The other point is: how much maintainer time is spent (not to say
"wasted") in figuring out these workaround, setting up blacklisting
code, maintaining the blacklist.
>> Just because the DAU of the day assumes his defaults are the only sane
>> ones doesn't mean everybody else shares his POV.
>>
>> Proper compact discs were meant to be written in streaming DAO mode, period.
>
> Totally agree with you! (But we have made already clear that's not what
> we are talking about)
Oh yes, it is - you want the burnfree default to change. Enabling
burnfree (even if Jörg chooses to reserve a particular exit code for
"success, but disc is nonconformant because {burnfree|tao|whatever} was
used") means that the default moves away from guaranteeing intact discs.
--
Matthias Andree
