Because two seconds on Terminal are easier than five minutes peering at your Database Manager Of Choice's query window. Nobody likes messing around with the db more than can be helped, hence the handy install script. What's the big deal?

I think the OP is referring to the fact that it could use the Updater classes (and log the update as completed) via update.php.

(In reply to comment #1)

Because two seconds on Terminal are easier than five minutes peering at your
Database Manager Of Choice's query window. Nobody likes messing around with the
db more than can be helped, hence the handy install script. What's the big
deal?

That has nothing to do with it... Reedy is talking about why its rolling its own method instead of using the defacto standard that uses the update.php magic.

At the time the script was written, I think update.php and friends sucked and didn't really support this stuff too well.

(In reply to comment #3)

(In reply to comment #1)

Because two seconds on Terminal are easier than five minutes peering at your
Database Manager Of Choice's query window. Nobody likes messing around with the
db more than can be helped, hence the handy install script. What's the big
deal?

That has nothing to do with it... Reedy is talking about why its rolling its
own method instead of using the defacto standard that uses the update.php
magic.

Ah, I misunderstood. I thought his gripe was with that the extension makes the db changes with a script, rather than posting the query stuff on the MWwiki extension page - for pasting into a query window. I know a lot of people who run their own sites don't have shell access and have to find workarounds.

I've changed the summary to clarify that we probably want to kill off that installer script.

IIRC there *are* already updater hooks in which should take care of setup when maintenance/update.php is run.

Should check to confirm there's nothing else that installer does that's necessary and go ahead and drop it out and update documentation to indicate using the regular updater channels.

• Bug 32456 has been marked as a duplicate of this bug. ***

The installer script does things like importing from $wgCheckUserLog and importing recentchanges into cu_changes...

Open patches that need reviewing (in dependent order):

• https://gerrit.wikimedia.org/r/#/c/307141/ Modernize CheckUser old logs import script
• https://gerrit.wikimedia.org/r/#/c/307253/ Add populateCheckUserTable script
• https://gerrit.wikimedia.org/r/#/c/307336/ Cleanup CheckUser setup and remove old files

Change 307336 had a related patch set uploaded (by Glaisher):
Cleanup CheckUser setup and remove old files

https://gerrit.wikimedia.org/r/307336

Excellent! I am very happy that someone has finally submitted a patch to do away with $wgCheckUserLog, among other things. I will try to review these in the next two weeks.

Change 307336 had a related patch set uploaded (by Glaisher):
Cleanup CheckUser setup and remove old files

https://gerrit.wikimedia.org/r/307336

Change 307336 merged by jenkins-bot:
Cleanup CheckUser setup and remove old files

https://gerrit.wikimedia.org/r/307336