3 ms·

JuliaDB declares support for 0.6 not 1.0 - http://juliadb.org/latest/ http://juliadb.org/latest/ Which package declared support for 1.0.0 and didn’t compile?

kgwgk 8y ago
A binary package will be available in CRAN for a given platform/version only if it works (it passes all the tests). It seems that Julia lets you install a non-working package without any warning (you will probably get errors when you run it, but I guess it may also fail silently which is worse).
- et2o 8y ago
  I was excited to try using Julia 1.0.0 today after a couple years since my last try and... couldn’t. None of the packages work with it yet. I guess I could go find an older version, but it seems like a problem that Julia will happily allow you to install a package it isn’t compatible with. What’s the point of the Pkg system then? CRAN’s model makes a lot more sense.
  - StefanKarpinski 8y ago
    Many packages have declared them selves compatible with any future version of Julia... which is clearly a lie. These need upper bounds on their version compatibility, but that will take some time to propagate through the system.
- kwertzzz 8y ago
  This is indeed a very good idea. In Julia, the package author defines the range of supported Julia version. Most package actually just say "version 0.6 or later". The JuliaDB package was just been updated preventing the installation on Julia 0.7 or 1.0: https://github.com/JuliaComputing/JuliaDB.jl/commit/8bf3057df154b7d0b592248bb3be98171dd28738 https://github.com/JuliaComputing/JuliaDB.jl/commit/8bf3057d... A automatic check as in R would indeed a better choice.
  - tavert 8y ago
    That will only prevent installation of master of the package or the immediate next few versions on 0.7. The old package versions without a julia upper bound remain available so users on 0.7 or 1.0 will just be held back to old versions of JuliaDB until a new release without an upper bound gets made.

kgwgk 8y ago

A binary package will be available in CRAN for a given platform/version only if it works (it passes all the tests). It seems that Julia lets you install a non-working package without any warning (you will probably get errors when you run it, but I guess it may also fail silently which is worse).

et2o 8y ago
I was excited to try using Julia 1.0.0 today after a couple years since my last try and... couldn’t. None of the packages work with it yet. I guess I could go find an older version, but it seems like a problem that Julia will happily allow you to install a package it isn’t compatible with. What’s the point of the Pkg system then? CRAN’s model makes a lot more sense.
- StefanKarpinski 8y ago
  Many packages have declared them selves compatible with any future version of Julia... which is clearly a lie. These need upper bounds on their version compatibility, but that will take some time to propagate through the system.
kwertzzz 8y ago
This is indeed a very good idea. In Julia, the package author defines the range of supported Julia version. Most package actually just say "version 0.6 or later". The JuliaDB package was just been updated preventing the installation on Julia 0.7 or 1.0: https://github.com/JuliaComputing/JuliaDB.jl/commit/8bf3057df154b7d0b592248bb3be98171dd28738 https://github.com/JuliaComputing/JuliaDB.jl/commit/8bf3057d... A automatic check as in R would indeed a better choice.
- tavert 8y ago
  That will only prevent installation of master of the package or the immediate next few versions on 0.7. The old package versions without a julia upper bound remain available so users on 0.7 or 1.0 will just be held back to old versions of JuliaDB until a new release without an upper bound gets made.