[mythtv] [mythtv-commits] mythtv/master commit: 1b66c0422 by Chris Pinkham (cpinkham)
cpinkham at bc2va.org
Wed Oct 12 00:36:17 UTC 2011
* On Tue Oct 11, 2011 at 03:43:04PM +0100, Stuart Morgan wrote:
> > Is this truly a copy routine? ie. It makes a duplicate and leaves the
> > original in place. Maybe I'm just not seeing the use case. Wouldn't
> > a routine that moves the file (and removes the original) be more
> > useful?
Once the copyfile is supported, creating a --movefile is trivial.
Patches welcome. :)
> I can think of at least one reason for having a copy function - portable media
> players. If I owned one I imagine I might want to copy over a film or episode
> of a series to the device so that I might watch it when away from home. It
> doesn't logically follow that I'd want to delete the original from my
> recordings or video collection.
This is one use case, as well as the ability to insert media into a remote
Storage Group by specifying a local source file and a remote destination.
That way you don't have to mount the file server NAS shares on the client
that just mounted the memory stick from your video camera. :)
I had a copy file patch in my mythcommflag binary for a long time because I
used it to test the remote writeable RingBuffer support, so I figured I
throw that functionality into mythutil when I created it.
More information about the mythtv-dev