New package: JuliaLibWrapping v0.1.0#156889
Conversation
JuliaRegistrator
commented
Jun 2, 2026
- Registering package: JuliaLibWrapping
- Repository: https://github.com/JuliaInterop/JuliaLibWrapping.jl
- Created by: @timholy
- Version: v0.1.0
- Commit: 16824d7a209edd8418f3db5bde87b9f03cd48b99
- Reviewed by: @timholy
- Reference: JuliaInterop/JuliaLibWrapping.jl@16824d7#commitcomment-187309016
- Description: Generate language-bindings for Julia-generated shared libraries
UUID: d61f35a8-f6af-436f-bc10-cee6b101f7bd Repo: https://github.com/JuliaInterop/JuliaLibWrapping.jl.git Tree: 47641fcfb644e7a5d962ed325e32f090a2c715eb Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3
Move the main package from the repo root into a JuliaLibWrapping/ subdir, sibling to the existing JLWInterop/. Previously the main package sat at the root and contained JLWInterop/, so the registered JuliaLibWrapping source tree would have shipped an unused copy of JLWInterop. Each subdir package now also carries its own LICENSE, as the General registry requires for subdir packages. - Move src/ ext/ test/ docs/ examples/ Project.toml README.md under JuliaLibWrapping/; add a short monorepo README at the root. - Fix the relative paths that crossed the moved boundary: examples/ols/build.jl (../../JLWInterop -> ../../../JLWInterop) and docs/Project.toml (JLWInterop source path; also add JuliaLibWrapping as a [sources] path so the docs env is self-contained). The build-env [sources] and test->examples paths move as a unit and stay valid. - Re-prefix the root-anchored .gitignore entries. - Rework CI to test both packages via a package matrix (setup-julia's project input resolves each package's own min), deploy docs from the subdir via a manual make.jl run, and point TagBot/CompatHelper at the subdir packages. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human. 1. New package registrationPlease make sure that you have read the package naming guidelines. 2. AutoMerge Guidelines which are not met ❌
3. Needs action: here's what to do next
If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the 4. To pause or stop registrationIf you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text Tip: You can edit blocking comments to add |