On Sat, Aug 19, 2006, EV wrote:
> Not necessarily: we could always resort to fill the path
> properties with genre/artist/tune by default.
And then you are back to the non-unique filename problem again.
> > for f in A*/*/*.{oog,mp3} Ella/*/*; do
> > cp $f mnt/tune/$f
> > done
> >
> > ie. you make it work exactly like a real filesystem. "cp
> > A/B/C.ogg mnt/tune/A/B/C.ogg" works, whilst "cp A/B/C.ogg
> > mnt/tune/" doesn't work.
>
> Well, it would work with "cp --parents ...".
Whatever. The point I was trying to make is that "cp A/B/C.ogg mnt/tune/"
should fail.
> > That way you don't have to worry about the duplicate file
> > issue. Any file named mnt/tune/A/B/C.ogg will get overwritten
> > and if you use "cp -i" it will prompt you first.
>
> But this method (which is the one already available with -T)
> assigns the properties artist="A", source="B", title="C",
> codec="ogg". Therefore, in the RK you'll see that the artist of
> this tune is "A", its album "B" and the title "C" (regardless of
> the labels in the tune's tag.
Exactly. If you want to copy a file using the tune's tag then you
either use riocp or use a script which extracts the tags before
performing the copy.
That way lkarmafs is guaranteed to work in a predictable way and
you don't have to worry about what happens when there is a filename
conflict.
Keith.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
linux-karma-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-karma-devel
