allow to overwrite just one track without cleaning the whole destination directory

[GoogleCodeExporter]

What steps will reproduce the problem?
1. rip for example a whole cd
2. try to re-rip one track of the same cd
3. answer the following question with "overwrite"
4. the entire directory with all the other tracks will be deleted

What is the expected output? What do you see instead?
I'd expect that just the one selected track is overwritten, and not the
complete directory deleted instead.

What version of rubyripper are you using? On what operating system? Are you
using the gtk2 or the commandline interface?
version of rubyripper is 0.5.0
operation system is gentoo
interface on that bug was gtk2, but i didn't test the command-line
interface if it behaves the same way, but i assume so.

Please provide any additional information below.
rubyripper itself is a great software, i really like it. :)

Original issue reported on code.google.com by harald.g...@gmail.com on 20 May 2008 at 5:13

[GoogleCodeExporter]

Why does this one comes up every time? It does state that it overwrites the 
DIRECTORY, not 
just the FILES, right? Do we really need a Windows-like pop-up? "Are you sure 
you wanna do 
that? You might lose some files!".

You get all kind of issues when I allow to overwrite files. For one, you need 
to update a logfile 
somehow. And it's really easy to auto-rename instead and manually merge the 
file back. 
After all this doesn't happen too often.

Original comment by rubyripp...@gmail.com on 20 May 2008 at 5:32

• Changed state: WontFix

[GoogleCodeExporter]

I can understand your view of the problem, and like you said it's stated that 
the
directory will be overwritten. I didn't think about the problem with the 
logfile,
when offering the option to just overwrite the file.

Auto-Rename is a good option to handle that problem, and this is allready 
offered.

Thanks for having a look at that.

Kind Regards,
Harald

Original comment by harald.g...@gmail.com on 23 May 2008 at 10:50

[GoogleCodeExporter]

I see the developer's side of this as well, as keeping a clean log file is 
important.

Here is my scenario though:  I switched over to Linux 100%, and found this to 
be one
of the best quality rippers for my needs... with the one exception mentioned in 
this
ticket.  It probably has to do with how I organize my music.

I rip to flac and mp3 at the same time, and use the %f designation.  Here are 
my file
creation strings:

%f/%a/%b - %n.%t

You see, I organize in folders by artist, into one folder by putting the album 
name
into the file name.  This gives me a single directory listing of any artist and 
shows
me all tracks I have at that level.

The problem comes in when I rip many albums, such as when I re-ripped my entire
collection to change some settings.  RubyRipper won't add an album to a 
directory in
the way I have my file structure set up.

It seems the only option I have is to write a script to parse and rename my 
entire
collection into another layer of folders, or re-rip to that structure.

It would be nice to have an "advanced" checkbox or such, that when checked, it 
just
writes files whether new or overwrites existing, doesn't gen playlist, and logs
everything to one file.

I know my situation may be unusual though.

Original comment by jh.xs...@gmail.com on 13 Sep 2009 at 3:36