Platform Development • Re: Autoconf dependency removal?

Mozilla's later implementation is also incompatible with how we do things. If we wanted to replace our vendored stuff (which works) with another tool, we'd just be locking ourselves to another tool -- and if it's not in-tree, we'd even run the increased risk of being targeted by a supply chain attack on our build system. I'd rather not.

Also, Athenian is right: I'd rather dial back moz.configure to use our configure/make system more than moving more towards python for it. We keep running into oversights in the python parts of the build system because things are so spread out in the tree (it's a hot mess, to be quite frank). But all of those ideas will cost a lot of time to parse and work through, which is in short supply.