On Fri, Nov 01, 2013 at 07:33:16PM +0000, Debian Bug Tracking System wrote:
> > If you intend for data loss to happen, then I'm afraid you're
> > completely oblivious to the concept of software and its users.
> >
> > Seriously now.
> >
> > % touch foo % touch foo.gz % gzip foo gzip: foo.gz already exists;
> > do you wish to overwrite (y or n)?
> >
> > You never came across this concept?
>
> This isn't the unix way of doing things:
>
> echo foo > bar
> cp bar baz
> tar cf foo.tar bar baz
> mv bar baz
The definition of the shell syntax for overwriting a file is explicit - you
have to type the ">" before the file name. cp and mv support -i and -n
options because they're aware of this problem. Even tar, whose c option does
blithely overwrite, has the user explicitly pick that option. Only script
overwrites entirely implicitly.
Where do you see the Unix consistency here, when out of half a dozen tools,
only two behave exactly the same way, and those two do provide a lifeline to
the user, as opposed to what script does?
On a more general note, I'm done with the reopening. In retrospect, after
the submission was ignored for over four years, and after it was rejected
with merely a rude oneliner, it was ridiculous to even start responding to
this. You've provided a new textbook example of how the Debian bug tracking
process can become an embarrassment to the project. It's really sad.
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
