#19021: collectstatic should only copy files if they have changed or don't 
exist in
destination
-------------------------------+---------------------------------------
     Reporter:  dloewenherz    |                    Owner:  dloewenherz
         Type:  New feature    |                   Status:  reopened
    Component:  Uncategorized  |                  Version:  1.4
     Severity:  Normal         |               Resolution:
     Keywords:                 |             Triage Stage:  Unreviewed
    Has patch:  0              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+---------------------------------------

Comment (by dloewenherz):

 Alright--I'm being educated here...I missed a bunch of things, but there
 are still a couple of problems. I noted them in an email to the developers
 list.

 The heuristic is not file name. Last modified time is the heuristic, but
 some backends don't have a reliable implementation of it (or don't support
 it at all) and therefore this feature doesn't work for those backends.

 Additionally, in any sort of source control, when a user updates their
 repo, local files that were updated remotely show up as modified at the
 time the repo is cloned or updated, not when the file was actually last
 saved by the last author. You then have the same scenario I pointed to
 earlier: when multiple people work on a project, they will re-upload the
 same files multiple times.

 For the reasons noted above, I would propose moving towards checksums and
 away from last modified times to check if a file has been modified.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/19021#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to