-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Michael raised a good point on IRC: <Herk> Theo makes a good point on the existing init.pre file, upgrades aren't going to get the new loadplugin lines added to their init.pre <jmason> well, it's exactly analogous to Apache's httpd.conf file <Herk> true, but can you disable some small piece of core functionality by not updating your conf file? I'm having trouble thinking of a concrete example in other types of servers <Herk> that match this case <Herk> FYI, I'm not -1 on the plugin, just stating an opinion that I don't believe having a plugin for the default case is needed/wise <jmason> hmm. you know, that's a point alright, this may cause upgrade issues. I hadn't considered that <jmason> specifically that 3.0.0 already has an init.pre, and we haven't currently got code that'll overwrite one of those so in other words, if users upgrade 3.0.x > 3.1.0, unless we add code to our installer to deal with this, it'll mean they'll have to manually edit init.pre to add loadplugin lines for the new default discriminator. - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Exmh CVS iD8DBQFB/sSHMJF5cimLx9ARAr5DAJ48oLP+8lqWWdaNl30ThILCZN2FOACgnxmn k2G76A+i5iZp3Ez21Po1z2E= =eObC -----END PGP SIGNATURE-----
