-
Notifications
You must be signed in to change notification settings - Fork 6
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
subdir issue #28
Comments
the simplest fix is to call If we just check julia> analyze_from_registry(find_package("SnoopCompileAnalysis"))
Package Invalid Project.toml:
* repo: https://github.com/timholy/SnoopCompile.jl.git
* uuid: 00000000-0000-0000-0000-000000000000
* is reachable: true
* no license found
* has documentation: false
* has tests: false
* has continuous integration: true
* GitHub Actions which isn't ideal since we don't even store what package it was. |
I wanted to avoid adding packages if possible, also because not all packages are installable in any given version of Julia |
Ok, makes sense. Maybe we should just go back to storing the name and UUID from the registry, and then we can have a separate field That way we can just give up here and at least have the right name of the package. (edit: though actually we should still at least have the repo and subdir.. so maybe we don't need the name) |
But yeah, I was aware that git cloning the latest version of the repository is dumb, as the repository may have changed layout since last released version. One thing we could look into is how Pkg gets the package. However I don't want to use the resolver for the reason above (we don't care about compatibility, also we don't need the dependencies etc...) |
Apparently Pkg.add gets the code by asking git for the tree hash that is stored in the registry (not totally sure how that works). So it's pretty robust bc the tree just has to exist somewhere in the repo history. |
One advantage of cloning the repo is we get access to the toplevel too, which often is where the CI scripts are, and sometimes the license. |
The problem is that the code for the package was removed in timholy/SnoopCompile.jl#127, so AnalyzeRegistry can't find it from cloning the repo (and it's not
Pkg.dev
'able). It's stillPkg.add
'able though, so we could get the code that way if we wanted.The text was updated successfully, but these errors were encountered: