Ignoring old evolutions in long-running project

I’m in a very long-running project with a lot of evolutions. As time has gone on, we’ve updated the database in both production and development environments, and some earlier evolutions no longer work in fresh databases.

For bringing up new developers, I’d like to modify the older evolutions so they apply cleanly; however, I don’t want existing DBs (for existing developers, or in server environments) to have to roll back to the modified evolutions, or to have to perform any error-prone or time-consuming manual changes.

Does anyone know a good way to get play-evolutions to ignore changes to very old scripts (say, everything below a certain number)?