Registration in the general registry

[grasph]

This issue is a placeholder to trigger registration of new release in the General Julia registry

[grasph]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/108095

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.3.0 -m "<description of version>" 4041abbfb938e7c60de6e51f7a701abcc03f342b
git push origin v0.3.0

Also, note the warning: This looks like a new registration that registers version 0.3.0. Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

[grasph]

@JuliaRegistrator register

Release notes:

This release brings support of modern Julia releases. Previous one required Julia 1.3.x or below.

Breaking changes

CxxWrap is now used instead of Cxx bringing major changes in the API. This was required to support recent Julia versions. While previous release was providing access to the full ROOT C++ API, thanks to the dynamic binding of Cxx, with this release we are limited to the classes, for which the binding has been implemented so far.

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/108095

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.3.0 -m "<description of version>" 4041abbfb938e7c60de6e51f7a701abcc03f342b
git push origin v0.3.0

Also, note the warning: This looks like a new registration that registers version 0.3.0. Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

[grasph]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/108095

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.3.0 -m "<description of version>" 05f7924526d347d8843b5c3a54b061a6c94e1b96
git push origin v0.3.0

Also, note the warning: This looks like a new registration that registers version 0.3.0. Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

[grasph]

ROOT.demo() has been fixed.

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/108095

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.3.0 -m "<description of version>" 8094ac289cc962c3fe1240c70f2100acef935bdc
git push origin v0.3.0

Also, note the warning: This looks like a new registration that registers version 0.3.0. Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

[oschulz]

That's done now. :-)

[grasph]

@JuliaRegistrator register

Release notes:

• Upgraded supported ROOT version to 6.32.02 (latest from Conda, when making this release)
• Support of TObArray
• Add move! function, to disable deletion of a C++ object allocated from Julia
• More convenient Get(::TFile,...) method, that returns an object of the expected with no need of cast anymore.
• Support of file["content_name"] and file.content_name in addition to Get(file, "content_name") to retrieve an object from a TFile
• Fix for compilation of ROOT libraries with clang (used on MacOS)
• Fix support of std::vector. For std::vector SetObject must now be used instead of SetAddress and Branch takes now a reference instead of a pointer.
• Branch() function has now default values for bufsize and splitlevel which becomes optionnal as in the ROOT C++ API.
• Support of TH2x, TProfile, TProfile2D added. The ll ROOT Hist library is now covered.
• Fix Fit function for ARM architecture.

---

Contributors to changes with respect to previous release: Philippe Gras and Pere Mato.

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/115246

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.3.1 -m "<description of version>" e62cdfab37740a15627c43830099fed29aa9f3ed
git push origin v0.3.1

[grasph]

@JuliaRegistrator register

Release notes:

• Fix "missing assert.h" error with ROOT installed with latest Conda repository contents.

---

Contributors to code update respect to previous release: Philippe Gras.

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/115473

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.3.2 -m "<description of version>" db1b524feeaf2d6d4e0f76cb82f26323e0a4c2f6
git push origin v0.3.2

[grasph]

@JuliaRegistrator register

Release notes:

• Use of _jll packages to install backend (ROOT_jll) in place of Conda and C++-Julia interface library (ROOT_julia_jll). Automatic installation supported for Linux only. On MacOS, the user must install the c++ root framework backend himself.
• A larger ROOT class set coverage: almost all classes of the Histogram and Geometry libraries supported.
• New examples: inspect_tree.jl and geometry library examples (geom/assembly.jl, geom/geomAlice.jl, geom/geomAtlas.jl)
• Argument names are now included in the Julia function definition and displayed when methods of a function are listed (e.g., by the TAB completion, online help, or method() call).
• Switch to ROOT v6.32.08 (works also with 6.32.06)
• Improved compilation on mechanism for the C++-Julia interface library (when not taking from the ROOT_julia_jll package). The ROOTprefs package is used to store compilation and backend installation preferences, that are stored in the LocalPreference.toml file.

---

Contributors to code update respect to previous release: Philippe Gras.

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/134038

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.4.0 -m "<description of version>" 77ccfb134860559662ce0322580360f5cb074dc7
git push origin v0.4.0

[oschulz]

Use of _jll packages to install backend (ROOT_jll) in place of Conda and C++-Julia interface library (ROOT_julia_jll).

Oh, that's great news!

[oschulz]

(Just a heads-up, just saw that registration is complaining about a missing [compat] entry for UnROOT.)

[oschulz]

I think ROOT.jl itself shouldn't actually depend on UnROOT, right?

[grasph]

the dependency is coming from an example that use UnROOT to read back a TTree written with ROOT.jl. Dependencies changed to limit it to the examples and test (that test also the examples).

[grasph]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/134038

Recommendation: add release notes

Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).

To add release notes, just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add release notes to this registration, just re-invoke JuliaRegistrator and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.4.0 -m "<description of version>" 5247feb9677d44f16f094ed1a1e7125c863f5f5c
git push origin v0.4.0

[oschulz]

Thanks @grasph !

[grasph]

@JuliaRegistrator register

Release notes:

• Use of _jll packages to install backend (ROOT_jll) in place of Conda and C++-Julia interface library (ROOT_julia_jll). Automatic installation supported for Linux only. On MacOS, the user must install the c++ root framework backend himself.
• A larger ROOT class set coverage: almost all classes of the Histogram and Geometry libraries supported.
• New examples: inspect_tree.jl and geometry library examples (geom/assembly.jl, geom/geomAlice.jl, geom/geomAtlas.jl)
• Argument names are now included in the Julia function definition and displayed when methods of a function are listed (e.g., by the TAB completion, online help, or method() call).
• Switch to ROOT v6.32.08 (works also with 6.32.06)
• Improved compilation on mechanism for the C++-Julia interface library (when not taking from the ROOT_julia_jll package). The ROOTprefs package is used to store compilation and backend installation preferences, that are stored in the LocalPreference.toml file.

---

Contributors to code update respect to previous release: Philippe Gras.

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/134038

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.4.0 -m "<description of version>" 5247feb9677d44f16f094ed1a1e7125c863f5f5c
git push origin v0.4.0

[grasph]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/134053

Recommendation: add release notes

Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).

To add release notes, just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add release notes to this registration, just re-invoke JuliaRegistrator and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.3.3 -m "<description of version>" 3f6c3a87791897e7246e95a45ca66d36a7b32250
git push origin v0.3.3

[oschulz]

@grasph this is only for x86 Linux, not for ARM Linux, right?

[grasph]

Indeed. Do you have a use case for ARM Linux? If you have a use case for ARM Linux, I can try to build the _jll for this platform.

[oschulz]

Do you have a use case for ARM Linux

Not urgently, no. We just finally have an NVIDIA ARM+GPU system and I wanted to give it a try. :-) But ARM is, as you probably know, definitely coming to the LHC grid and HEP computing in general, so we should support it, if possible. Does the _jll have to be built "manually", or can we automatize it?

[grasph]

moved ARM support discussion to a new Issue, #31