chromium: remove redundant `run_mksnapshot_default` build target

This build target, mksnapshot, was added all the way back in 2014 in
8d54dc6d13ac3b42e45d95a2cfb971e7c01ad39c to add support for grsecurity.

A few years later in 2017, grsecurity made their free testing patches
private, forcing nixpkgs to drop the grsecurity-flavored linux
kernel in 32b8512e54b864ecf8c2b1e115c1a3f18e90a8c3.

Roughtly another year later, 1b146a8c6f55b23981c3817d8346f95bb3a799fe
removed paxutils from the stdenv and the remaining paxmark invocations
in various build expressions. The explicit mksnapshot build target,
however, remained, for no reason.

In 2023, 0a05fbb9a010337454b942011bfa92168b2efc17 renamed the target
from mksnapshot to run_mksnapshot_default for cross-compilation reasons.

Note that removing it does not improve compile times in any meaningful
way. This is because mksnapshot is implicitly pulled in by the main
build target, chrome. It does, however, make the ninja task count
more accurate and build dependency errors that would previously only
happen in chrome but not mksnapshot, no longer require to first build
mksnapshot and instead fail immediately.

0 files changed, 0 insertions, 0 deletions