I thought that the new package manager has the big advantage that if package A requires package B in the version defined in the Project.toml file, then whenever A is used, it uses package B with this version, under all circumstances (so using package A is reliable). However, by accident I recognize…

deving a package makes all of your packages utilize this development version. This is to make it easy to see how a package modifies others. If you want to prevent this behavior, then you should develop in an environment. But just to be clear, a user will get 0.2.4.

I tested with a clean environment that contains no development version. Here is the log: _ _ _ _(_)_ | Documentation: https://docs.julialang.org (_) | (_) (_) | _ _ _| |_ __ _ | Type "?" for help, "]?" for Pkg help. | | | | | | |/ _` | | | | |_| |…

That environment isn’t clean. It has ModaMath dev installed.

O.k. I removed ModiaMath and tried to add ModiaMath, version 0.2.3: (v1.0) pkg> status Status `HOME\.julia\environments\v1.0\Project.toml` [cb905087] Modia v0.2.2 [d330b81b] PyPlot v2.6.3 (v1.0) pkg> add ModiaMath@0.2.3 Resolving package versions... Updating `HOME\.julia\environments\v1…

I think some things need to be clarified: Only one manifest is used, in particular, the toplevel one. When you add Modia the Manifest.toml file in Modia is ignored. Only one version of a package can be loaded (specified from by the toplevel Manfest.toml), so Modia will never use “its own” version,…

[image] fredrikekre: I think some things need to be clarified: Only one manifest is used, in particular, the toplevel one. When you add Modia the Manifest.toml file in Modia is ignored. Only one version of a package can be loaded (specified from by the toplevel Manfest.toml ), so Modia will ne…

Thank you for the clarification. Obviously, I have misunderstood the new package manager. The consequence seems to be that a “normal” user (who is using Julia and packages from the Julia community for production work) needs to rely on pre-configured distributions (such as JuliaPro), where someone t…

[image] MartinOtter: The consequence seems to be that a “normal” user (who is using Julia and packages from the Julia community for production work) needs to rely on pre-configured distributions (such as JuliaPro), where someone takes the effort to combine compatible packages in a distribution. …

[image] fredrikekre: No. You should not make releases of your packages that are not compatible. Sure, I agree. However, if by accident a non-backwards compatible change is made to a package, say ModiaMath 0.2.5, and then a user package A is used (which uses ModiaMath 0.2.4), then A is correct…

[image] MartinOtter: I hoped that this situation would be solved by the new package manager, but it seems this (very hard) problem is still pending. I think this is a mostly orthogonal problem, and is best tackled but other tools (including CI).

Modia requires ModiaMath 0.2.4 but uses 0.2.5-dev (surprising behaviour)

General Usage

Sukera October 14, 2018, 6:03pm 8

No, this has nothing to do with REQUIRE. See here.

Topic		Replies	Views
Pkg.add() refuses to use the required version General Usage	9	2518	August 14, 2018
ModiaMath has no know versions (although 3 versions released) General Usage diffeq	3	544	September 21, 2018
JuliaCIBot on Modia fails for Julia 1.0, but Travis is successful General Usage	8	933	October 8, 2018
Where does Pkg(3) find version numbers? Internals & Design	19	2574	August 14, 2018
A slight flaw in the Project/Manifest/Env logic? General Usage	7	667	June 14, 2020

Modia requires ModiaMath 0.2.4 but uses 0.2.5-dev (surprising behaviour)

Related topics