- None: as before, doesn't generate any bound
- Current major version: will restrict to the major version of the package you currently have
- Current major version from current minor: the minor version of the package you currently have is going to be the lowest version allowed, up to the next major version. This is the default, since it assumes the current version you have is the one you're testing against
- Current minor version: only use the minor version of the package you currently have
Thursday, August 29, 2013
EclipseFP: package version bounds in dependencies
Coming in EclipseFP 2.5.5, the cabal editor lets you specify what policy you want to use in respect to versin bounds when adding a dependency to a package, instead of just referencing the package without any constraints, or having to type them by hand:
The text field shows you the actual values that get generated. This field is now read-only since you can first select a package then change the version restriction options. If you want to enter manually the version bounds, you can still do that on the main page where all the current dependencies are listed.
I hope it will let you conform to the Package Versioning Policy and provide reasonable dependency bounds on your libraries.
No date on the 2.5.5 release yet, there's a couple of things I'd like to do first. The Github version should be usable if any of you want to live on the edge (and perform some valuable testing!).