No. User has to delete old package repository, new format is it not compatible with other one <https://github.com/nim-lang/nimble/issues/940#issuecomment-919901395>. I can't use any older compiler version with new repository format as well. In addition, 'nimble develop' has been remove and there is no alternative to it (this has been explicitly said in one of the previous comments). Also new description of the features in readme is completely inaccessible for those who just want to answer simple questions like "how do I migrate if I extensively used old nimble develop?". New readme mixes implementation details with everything else and is written in C++-standard style ... not really readable. And this only makes matters worse, since everyone would have to dig through this. The format for included develop files is the same as the project's develop file, but their validation works slightly different. Validation rules: The included develop files must be valid. The packages listed in dependencies section must be dependencies required by the package's .nimble file and to be in the required by its version range. Transitive dependencies are not allowed, but this may be changed in the future. The packages listed in the included develop files are required to be valid Nimble packages, but they are not required to be valid dependencies of the current project. In the latter case, they are simply ignored. The develop files of the develop mode dependencies of a package are being followed and processed recursively. Finally, only one common set of develop mode dependencies is created. In the final set of develop mode dependencies, it is not allowed to have more than one package with the same name but with different file system paths. Run
Like who needs this in the readme? It is a `format_spec.md`, unless you are implying users should just roll their own package manager to use this thoroughly described format.
