There is zero reason that this shouldnt be in an extension. Basically a few users want to install a shinny new toy called swiftmailer into core, just because its shiny. In doing so they add a complexity and headache. Such a addition should be done as an extension
On Tue, Jun 10, 2014 at 11:55 PM, Isarra Yos <[email protected]> wrote: > On 11/06/14 03:31, John wrote: > >> My suggestion, "Flip the fuck out" Its a really bad idea that wasnt >> thought >> though, If users want SwiftMailer support it should be done in an >> extension, and not in core >> >> On Tue, Jun 10, 2014 at 11:30 PM, Isarra Yos <[email protected]> wrote: >> > > Okay, so I'm completely lost. Is the idea here that SwiftMailer is some > shiny new thing that introduces new features, but also new dependencies and > whatnot, and that MediaWiki as a whole won't work without the dependencies > involved? > > If so, does it really need to be in core? And if it doesn't, why isn't it > an extension? > > And even if it does need to be in core, why should it mean MediaWiki > should no longer be installable from git? MediaWiki already has > dependencies (which are generally met for all wikis when several are > already installed), and the installation process either allows you to > progress or not depending on whether or not they are met, but it does at > least start out of the box. Why should this be any different? Is this > really a sane transition/requirement for developers running test instances, > for third-party projects running from git, and other users? > > And, again, what's the purpose of it in the first place? > > -L > > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
