I must've misunderstood how 'creates=' is implemented, sorry. it makes no sense to me that the type of archive would make any difference; surely if a 'guard' is there (that's just checking if a file path exists) that should prevent the task from running regardless of what the task is?
Can anyone with a better understanding explain this? On 2 February 2016 at 11:41, Tuomas-Matti Soikkeli <[email protected]> wrote: > I believe it's because zip doesn't support it like tar does. So I suppose > there is no fix for that other than manually comparing the contents with > python ZipFile api. Unfortunately zip lacks most of the unixy features which > tar provides like user/group modes, modification date and so on. > > So the final question is do we choose convenience over control? Just check > file sizes from headers and don't extract if matches. Is this reasonable or > unacceptable? > >> it might be easier to figure out >> why creates= is too slow for you and fixing that. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAK5eLPQjntNOOeP6j0mn%3D9i01WPWM-vTutRPqNuyJn8%2B5Cm30Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
