There will always be a way to opt out. For applications I think we do not care, since if all dependencies are conforming to the naming requirement, then in the main application you can use any scheme you want. That is the whole point of having these restrictions.
So if I want to take two existing but related projects, P1 and P2 and combine them into a new package,
or copy different components together to make a build of an application that is stand-alone that is made up of many existing non-fpm packages following no convention, or multiple fpm dependencies and want to place them all in the same package nothing would have to be renamed? That does not seem to fit the description of the change, especially if I want to combine some projects into a single project.
@urbanjost to answer your question, in my mind you would need to use some compiler option to fpm to disable the naming restriction checking. (It’s yet to be designed if it should be a compiler option, or an option in your final application fpm.toml, etc.) So yes, your use case would be possible, but it would be “opt in”.