Hey, > The solution proposed by Hashar in some other thread is to have a > > "MediaWiki installation" package, which just contains a composer.json > file > > with core in it, where people can add dependencies, and then install. > > Before that will work, we'll need to get rid of "global scope > assumptions" > > in all core files. For instance, WebStart.php has globals in it, accessed > > without specifying they are globals. This will break when included via > > Composer, as it will not do so in global scope. > > > > > Easier said than done. I've been fighting this fight for years and we're > only about 3 globals closer to doing so. I'm totally in favor of getting > rid of global scope usage, but let's please not trivialize the amount of > work it will take to get there. >
> Easier said than done. Certainly. Else it would probably already be done :) > I've been fighting this fight for years and we're only about 3 globals closer to doing so. I suspect you are not understanding me correctly after reading that. I'm talking about referring to global variables as if they where local variables (thus without the "global" keyword) which happens to work if your code is being executed from global scope, but breaks when it is included from any other scope. Getting rid of all globals would be an humongous task and one that is simply not feasible in a short period of time. Luckily we do not need to do this to have core work with Composer. > but let's please not trivialize the amount of work it will take to get there. I certainly did not mean to imply doing this is trivial, as I agree with you it is a lot of work. That is why I'm listing this as one of the main obstacles. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
