#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: nobody
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
------------------------------------+-------------------------------------
Comment (by aaugustin):
Replying to [comment:9 gnotaras]:
> All in all, I'd like to clarify that I did not mean to complain about
''collectstatic''.
Sorry if my comments sounded too harsh. We're all trying to make Django as
useful as possible.
[[BR]]
> The way it currently works is fantastic. The only issue I encountered
occurs only if the '''-l''' switch is used, in which case any files inside
STATIC_ROOT that are not found by the static-finders are replaced by
symlinks-to-self. If '''-l''' is not used, then everything works fine. I
am sorry if I did not clarify it from the beginning.
Yes, I understand this.
I think we have to choose between the following three options:
- 1) just fix the problem with the "-l" switch; it's an improvement, but
we still have an underdefined behavior when `STATIC_ROOT` contains extra
files (either added manually to `STATIC_ROOT`, or removed from
`STATICFILES_DIRS`), and we're exposed to the [comment:9 data-loss problem
I explained];
- 2) normalize the behavior of `collectstatic` by removing any extra
files; but that's backwards incompatible for people that rely on the
current, undocumented behavior;
- 3) same as 2), but with a command-line option to control whether
`collectstatic` will clean up unused files; the default value of this
option is debatable (backward compatibility vs. predictability).
--
Ticket URL: <https://code.djangoproject.com/ticket/16161#comment:10>
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 this group at
http://groups.google.com/group/django-updates?hl=en.
