On 10-11-09 03:42 PM, Platonides wrote:
Trevor Parscal wrote:
In relation to:
https://bugzilla.wikimedia.org/show_bug.cgi?id=25124 - I
am considering removing $wgStyleDirectory rather than further depending
on it.
It seems that it's only partially used right now, and making the style
directory variable but not other directories is inconsistent as well.
There was some point about this being a feature that makes MediaWiki
more flexible, but I'm unsure this is actually adding flexibility, it
seems more like unnecessary complexity.
I'm considering just removing it - any points to the contrary would help
me make this decision.
- Trevor
Backwards compatibility.
Some systems may not support symlinks
$wgStylePath would be sad if you killed $wgStyleDirectory
(we provide them in pairs)
Is it that hard to support it?
That's a -1 here too, we should be trying to improve flexibility, not
drop existing flexibility. If resourceloader isn't listening to
$wgStyleDirectory then it's a bug that should be fixed, unless
resourceloader has a damn good reason for ignoring existing configuration.
Frankly, for awhile now I've wanted to fix MediaWiki's dependence on a
single directory for skins. Currently installing a new skin requires
adding a file or two and a directory into skins/. Whilst installing an
extension, besides the LocalSettings.php tweak only requires dropping in
a single directory. IMHO extensions should be able to provide new skins,
just as extensions can currently provide new Special Pages. And the path
to where default skins are fetched should be left configurable for those
wanting to share skins between installs.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [
http://daniel.friesen.name]