-
-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installation section gives misadvice about version (at least for 0.x.y.z) #434
Comments
@dpwiz Ok I can understand the argument for the 0.x version series. Can I let you submit a patch? This is the bit of code you want to modify: flora-server/src/web/FloraWeb/Pages/Templates/Packages.hs Lines 475 to 483 in bc2a869
|
@dpwiz Do you still wish to tackle that one or can I reassign it? |
3 tasks
closed by #490 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It says
In your cabal file: acme-example ^>= 0.1
. But it doesn't know the actual version policy for the package.Of course, there's PVP with MAJOR.MAJOR.MINOR.PATCH scheme. But even if we ignore all the explicit non-practitioners there's something like a custom for "experimental", where the "epoch" major being
0
, shifts the breaking part further to the right.Ideally the packages should signal their "breaking" scheme somewhere in the package description, but that's outside the Flora powers (
x-breaking: 0.x.y
, anyone?).I think at least a hack for
0.x
would make the advice a bit more resilient by recommendingacme-example ^>= 0.1.2
instead.The text was updated successfully, but these errors were encountered: