[FFmpeg-trac] #11139(undetermined:closed): Option to preserve filetime of input

[FFmpeg]

#11139: Option to preserve filetime of input
-------------------------------------+-------------------------------------
             Reporter:  Ulf Zibis    |                    Owner:  (none)
                 Type:  enhancement  |                   Status:  closed
             Priority:  wish         |                Component:
                                     |  undetermined
              Version:  unspecified  |               Resolution:  wontfix
             Keywords:  convenience  |               Blocked By:
  option                             |
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Comment (by Ulf Zibis):

 Replying to [comment:1 inof]:
 > A better solution is this (after running FFmpeg):
 > {{{
 > touch -r <input> <output>
 > }}}
 You could also argue, that {{{ rm <output> && ffmpeg ... }}} is better
 than `ffmpeg -y`. Its's the same scope of actions.

 > Keep in mind that there can be an arbitrary number of input files (not
 just one), and there can be an arbitrary number of output files as well.
 What time stamp should be mapped from which input file to which output
 file?
 Use the same rules as for mapping files, streams and channels. If not
 otherwise specified, always refer the first input. Additionally allow
 specification like for all other mappings. Output is automatically
 specified by the position in the command. E.g., if `--codec` is placed
 after the first output file, it is only valid for the following output.

 > It's not that easy; a simple command line option won't suffice.
 Agreed, slicely more complex than for option `-y`
 > And what if the output is a symlink?
 Same question appears for option `-y` and your "better solution" !
 > What about the access time stamp, should it be preserved, too?
 Same question appears for your "better solution" !

 > Also, if FFmpeg started supporting that, then why not also preserve the
 files' permission flags? Or the group ownership?  Or ...?  It's a can of
 worms.
 Still same question appears for your "better solution" !
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11139#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker