> If it is executed in a package directory it adds cloned packages to the > special nimble.develop file. This is a special file which is used for holding > the paths to development mode dependencies of the current directory package. > It has the following structure:
>From <https://github.com/nim-lang/nimble#nimble-develop> by @bobeff > There is no equivalent of the old nimble develop. Now the develop mode > dependency packages are per project. There are no global development mode > packages. >From <https://forum.nim-lang.org/t/8404#54212> by @bobeff > The major difference is that the new develop mode has its effects restricted > to specific projects. You can have different overrides in different projects > (or groups of projects) specified by a nimble.develop placed in the project > directory. The rationale for this is that the old develop mode was too > polluting. > > To some **extent, simulating** the old develop mode is also quite possible. > You can create one global nimble.develop file and then define some command > aliases that manipulate it and include it automatically in your projects. >From <https://forum.nim-lang.org/t/8404#54497> (emphasis mine) by @zahary > nimble develop is not going away. It is enhanced with new features that > precisely try to make it more practical to work with a large number of > develop mode packages ... >From <https://forum.nim-lang.org/t/8404#54514> by @zahary Can this just be explained from the scratch - is that change breaking because "There is no equivalent of the old nimble develop.", or it is "not going away. It is enhanced with new features"? If there is no alternative to old nimble develop then how is it possible to "continue to work exactly as you did before."
