Implement Versioning about pony-stable HOT 4 CLOSED

@Vorlent can you clarify "has no concept of versions"?

do you mean, that dependencies always use HEAD? if yes, then that isn't the case. However, there are certainly improvements that can be made. It doesn't for example, do ranges. You can use a specific git tag/commit. For example...

https://github.com/WallarooLabs/wallaroo/blob/master/machida/bundle.json#L8

from pony-stable.

Okay I didn't know about the ability to specify versions inside tags.

Handling the minor and patch versions with tags this way is perfectly okay as long as the library does not have any breaking changes. But when backwards compatiblity is broken you need to be able to use two major versions of the same library in one program. Does pony-stable handle this in any way?

Let's take the pony-inspect library. Suddenly one day version 2.0.0 of pony-inspect is released. How do I use it via pony-stable?

Does pony-stable offer a solution beyond just putting the major version into the package name like this?

use "inspect"
use "inspect2"

from pony-stable.

you would change the version in your bundle.json to match the API you are using in your code:

{
  "deps": [
      { "type": "github",
        "repo": "jemc/pony-inspect",
        "tag": "2.0.0"
      }
  ]
}

you would version your bundle.json along with your changes to upgrade to whatever the API changes were for the new version of pony-inspect.

from pony-stable.

Ok. Thank you.

from pony-stable.