I have a project with a few local packages. Some packages use dev path/to/Package to use another package, but this only works for one level. That is, if activate PkgB and do dev path/to/PkgA, then if we activate PkgC and do dev path/to/PkgB, we’ll get a warning about “Unsatisfiable requirements dete…

[image] tuckermcclure: Here are those commands: Would it be possible for you to update to v1.4? It looks like this exact set of commands now works. My hypothesis is that newer versions of Pkg are now able to look into B’s manifest to find where A comes from… Of course, you’ll have to commit …

One silly work-around is to have PkgC first dev PkgA and then dev PkgB. With many little packages, this becomes very tedious.

Thanks @fredrikekre . I think by this: dev them all at once instead. you mean dev PkgA PkgB, no? If so, that’s not really getting at the problem. The point is that PkgC now has to dev all of the local dependencies for every package it uses, which is hard to maintain. That is, if you add a new de…

[image] tuckermcclure: The point is that PkgC now has to dev all of the local dependencies for every package it uses, which is hard to maintain Yes, that’s unfortunate, we have this “problem” too. I think the solution is to either avoid having too many small packages, or to bite the bullet an…

[image] cstjean: We did it recently with LocalRegistry.jl, and it wasn’t that bad, but we aren’t tagging yet, which is AFAIK required for the solution to the transitive dependency problem. I’m not quite sure what you mean here. Git tags are useful in many ways but they play no part in Pkg dep…

Yes, I meant “registering tree hashes”. We do not register tree hashes with regularity in our registry (except the first registered tree hash, of course). If A’s environment depends on B’s master, and B “depends” on C’s master, then adding A will add C’s latest registered tree hash, and not C’s mast…

[image] cstjean: We did it recently with LocalRegistry.jl… Hey Cédric, I think this still requires that each package is a git repo though, right?

Yes! Sorry, I missed that part of your original post.

[image] tuckermcclure: Hey Cédric, I think this still requires that each package is a git repo though, right? For now, but it’s not a fundamental restriction. Pkg can already handle packages that are subdirectories of a git repository in a limited capacity, see https://github.com/JuliaLang/Pk…

"Unsatisfiable requirements" when local packages use local packages (fixed in v1.4)

General Usage

tuckermcclure April 3, 2020, 1:00am 6

This thread mentions a broader set of the problems experienced here: Could we make first-class support for packages that are "just files" and not repositories?

Topic		Replies	Views
Developing interdependent, local, unregistered packages General Usage question , package	18	1603	June 20, 2024
Pkg(3): develop package which depends on local/unregistered package Internals & Design question	23	5157	August 6, 2018
Unregistered dependencies do not work with unregistered package General Usage pkg , package-manager	2	723	June 7, 2022
Unsatisfiable requirements error between my personal packages Package Management compatibility	5	353	March 9, 2023
Could we make first-class support for packages that are "just files" and not repositories? General Usage packages , package-manager	21	2677	October 16, 2021

"Unsatisfiable requirements" when local packages use local packages (fixed in v1.4)

Related topics