Skip to content

New package: librel_ant_parser_jll v0.0.1+0#147694

Open
JuliaRegistrator wants to merge 1 commit intomasterfrom
registrator-librel_ant_parser_jll-f30bf88c-v0.0.1+0-7652f83ea6
Open

New package: librel_ant_parser_jll v0.0.1+0#147694
JuliaRegistrator wants to merge 1 commit intomasterfrom
registrator-librel_ant_parser_jll-f30bf88c-v0.0.1+0-7652f83ea6

Conversation

@JuliaRegistrator
Copy link
Contributor

UUID: f30bf88c-a969-5e45-b2c9-3eb7c20c1c7d
Repo: https://github.com/RelationalAI/librel_ant_parser_jll.jl.git
Tree: e21d93f8c24ebf875612e4dc16cedf69a911b975

Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3
@github-actions
Copy link
Contributor

github-actions bot commented Feb 5, 2026

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 registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines which are not met ❌

  • Name does not meet all of the following: starts with an upper-case letter, ASCII alphanumerics only, not all letters are upper-case.
  • Version number is not allowed to contain build data

3. Needs action: here's what to do next

  1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
  2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

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 #pkg-registration channel in the public Julia Slack for better visibility.

4. To pause or stop registration

If 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 [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

@Drvi
Copy link

Drvi commented Feb 5, 2026

[noblock] A little clarification on why I'm registering this "JLL" package manually (which I've also shared in the #new-packages-feed Julia slack channel): I can see there are several other “manual JLL” packages, e.g. Gurobi_jll. I think for Gurobi_jll, the manual approach offered a way to comply with their commercial licence, for us this is about being able to publish a new version of the JLL without needing to wait for an approval on the Yggdrasil repo (since the --deploy feature of BinaryBuilder.jl makes the process already pretty seamless, IMO!). Maybe in the future, once the package fully stabilizes, it would be best to have the recipe in Yggdrassil, but right now I’d love to have a more direct control over the release, if that is an option. Right now this package is vendored in our project and is build with a Pkg.build step which hinders precompile-ability and is a source of problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants