New package: ROOT v0.3.0

[JuliaRegistrator]

• Registering package: ROOT
• Repository: https://github.com/JuliaHEP/ROOT.jl
• Created by: @grasph
• Version: v0.3.0
• Commit: 8094ac289cc962c3fe1240c70f2100acef935bdc
• Reviewed by: @grasph
• Reference: Registration in the general registry JuliaHEP/ROOT.jl#22 (comment)
• Description: CERN ROOT compatiblility for Julia

[github-actions]

Your new package pull request does not meet the guidelines for auto-merging. Please make sure that you have read the General registry README and the AutoMerge guidelines. The following guidelines were 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.
• Name is not at least 5 characters long

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

After you have fixed the AutoMerge issues, simply retrigger Registrator, which will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number).

If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the Julia Slack to ask for help. Include a link to this pull request.

Since you are registering a new package, please make sure that you have also read the package naming guidelines: https://pkgdocs.julialang.org/v1/creating-packages/#Package-naming-guidelines

---

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. You can edit blocking comments, adding [noblock] to them in order to unblock auto-merging.

[goerz]

Does this really need conda as a dependency?

[goerz]

(Let me hold off on the "needs to be merged manually in 3 days" tag, since at least the compat-issues need to be fixed before it's ready to merge)

[grasph]

The library it wraps is installed with Conda. Ultimately the BinaryProvider will be used, but the cross-compilation is a challenge for the ROOT library source, which is not yet solved yet (JuliaPackaging/Yggdrasil#7666). Use of Conda was a compromise in order to move on with the distribution of this wrapper.

For the compat specs what is the recommendations? Should I used major.minor of the latest version?

[goerz]

Should I used major.minor of the latest version?

That's what I usually do. Or, hypothetically, you could try to find out what are the oldest versions that actually work (make sure to have an entry in your test matrix that installs your dependencies in their declared oldest versions, to make sure it actually works and to tell you when you need to bump the compat entries).

[grasph]

Can we proceed with the merging of this PR?

Let me know if I can do anything on my side. I don't understand the logs of AutoMerge: all the messages before the exception say "meets_this_guideline = true", but may be it is due to the package name, which requires a manual merge as discussed earlier.

Thanks,
Philippe.

[goerz]

You’re okay, the only thing to do is to periodically ping the #pkg-registration channel on Slack. Usually things get merged quickly, but there’s been a backlog the past week. There’s a pretty small group of full maintainers who have merge permission, and maybe they’re all traveling/busy/on holiday, or something

[grasph]

Thanks @goerz for this information. I've posted a message on the Slack channel.

[grasph]

Thanks @ericphanson for the merge.