-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter Gordon wrote: > Adrian Reber wrote: >> I am thinking about to disable this feature in the Fedora rpm because >> the update is anyway supposed to be updated via yum/rpm and not by >> downloading it directly from wordpress. Just like it is the case for >> firefox. >> > > +1; I did that for Deluge, too. > > For Deluge it was far simpler to patch the installed GConf schema to > set the key for that preference to False to default rather than True. > I've not delved much into the WordPress codebase, but whether it will > be simpler to remove the feature entirely or merely have it disabled > by default is a choice left to you, its maintainer. :) You can disable it via a plugin: http://wordpress.org/extend/plugins/disable-wordpress-core-update/ Stripping the code revision after revision may not be the best notion, from a support standpoint. Also, if you feel like it, there's a plugin to disable plugin update checking as well: http://wordpress.org/extend/plugins/disable-wordpress-plugin-updates/ - -- - ---------- Doug Stewart Senior Systems Administrator/Web Applications Developer Lockheed Martin Advanced Technology Labs dstewart@xxxxxxxxxxxx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHDQGbN50Q8DVvcvkRAuCgAJ4hOCEeMpLXqnoubnnNnXXbmz9WqACfb/Uh m0/8tXQu62Ah1FjhEO1Hz3c= =GUki -----END PGP SIGNATURE----- -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list