> The real reason that drives me to this though is that you > can't apply updates without being uid=1, and that is a > particular responsibility I wanted to share amongs admins in > my dev shop. I know that I can hack update.php but people > keep forgetting to "unhack it", so I was hoping to find a better way.
FWIW, I would support a core patch that adds a permission to "Run updates". admin_menu exposes this link as well, and can only expose it for uid 1. I see no compelling reason why only uid 1 should be able to run update.php (when the database is available). sun
