On 09/01/13 11:23, Arran Cudbard-Bell wrote:
That's the point of making things consistent, so you don't have to waste time referring to the man pages and documentation.
Just to point out: this change is not without cost. Thousands of sysadmins will have significantly more work upgrading their configs as a result. I'm all for rationalisation, but TBH you're not selling me on the cost/benefit tradeoff. Your choice, of course. But you shouldn't be surprised if this kind of thing significantly retards deployment of 3.0.
Also adding a module specific prefix to 'file' is wrong. You know what type of file it is by the module section it's declared in. The only place this would be of use would be in a completely flat namespace.
It may be "wrong" but it's what we CURRENTLY DO. Telling people "Hey we've changed our minds that thing we made you all do is now wrong" just irritates them. Can we at least maintain backwards compatibility for one major version to read the old filenames? Surely it can't be that hard to have a short lookup table from the old names?