#16161: If extra static files are added into STATIC_ROOT, they are transformed to symlinks in the next run of ``collectstatic -l`` ------------------------------------+------------------------------------- Reporter: gnotaras | Owner: aaugustin Type: Bug | Status: new Milestone: | Component: contrib.staticfiles Version: 1.3 | Severity: Normal Resolution: | Keywords: Triage Stage: Accepted | Has patch: 0 Needs documentation: 0 | Needs tests: 0 Patch needs improvement: 0 | Easy pickings: 0 UI/UX: 0 | ------------------------------------+-------------------------------------
Comment (by jezdez): Having thought more about the issue Luke was mentioning, I don't believe I agree that his is an actual problem. In fact I might want old files (such as pre-compressed stylesheet files) to stay in `STATIC_ROOT` to make sure users with cached pages or templates referring to those files don't break. In any case, I believe that the simplest way of "fixing" the issue Luke mentioned is to simply to delete `STATIC_ROOT` manually, because Django can't really forsee whether the files should stay around or not. That actually makes me wonder if the simplest solution would be: - add a ``--clear`` option that would try to delete the content of `STATIC_ROOT` if the user wishes, with the downside of having to wait **much** longer for collecstatic to run - fix the linking support to actually check if the to be symlinked file doesn't actually have the same name as the link -- Ticket URL: <https://code.djangoproject.com/ticket/16161#comment:19> 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 django-updates@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.