Adding diffpy.srreal

[Tieqiong]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory. You can also examine the workflow logs for more detail.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16689553658. Examine the logs at this URL for more detail.}

[github-actions]

Hi! This is the staged-recipes linter and I found some lint.

File-specific lints and/or hints:

• recipes/diffpy.srreal/meta.yaml:
  • lints:
    • The following maintainers have not yet confirmed that they are willing to be listed here: pavoljuhas, sbillinge. Please ask them to comment on this PR if they are.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/diffpy.srreal/meta.yaml) and found it was in an excellent condition.

[Tieqiong]

@pavoljuhas @sbillinge please can you comment on this PR if you are willing to listed as a conda-forge maintainer for this package? Thanks!

[pavoljuhas]

@pavoljuhas @sbillinge please can you comment on this PR if you are willing to listed as a conda-forge maintainer for this package? Thanks!

Hi @Tieqiong - please remove me from the list of maintainers.

[sbillinge]

I am happy to be listed as a maintainer on this package

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/diffpy.srreal/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/diffpy.srreal/meta.yaml:

• ℹ️ You should not need to depend on libboost directly. If your package is linking to boost libraries, use libboost-devel in the host environment (which will create the correct dependence at runtime through a run-export), or use libboost-headers if you only need the boost headers.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16696645878. Examine the logs at this URL for more detail.}

[Tieqiong]

@conda-forge/help-python-c, ready for review!

[sbillinge]

• You should not need to depend on libboost directly. If your package is linking to boost libraries, use libboost-devel in the host environment (which will create the correct dependence at runtime through a run-export), or use libboost-headers if you only need the boost headers.

@Tieqiong The linter doesn't like this change, but this was needed for the CI to pass on windows, correct? If there is a way to make both the CI and the linter happy, we would be happy to hear it when it is reviewed by conda-forge

[Tieqiong]

@sbillinge Exactly. I already tried 1. no boost in run and wait for run_exports, 2. include libboost-devel in run, and 3. include libboost in run. Windows build only like 3, or it'll bump into error:

Needed DSO Library/bin/boost_serialization.dll found in ['conda-forge/win-64::libboost==1.86.0=hb0986bb_3'] but ['conda-forge/win-64::libboost==1.86.0=hb0986bb_3'] not in reqs/run, (i.e. it is overlinking) (likely) or a missing dependency (less likely)

[Tieqiong]

@conda-forge-admin, please ping team
Friendly ping 🙂

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-webservice.

I was asked to ping @conda-forge/staged-recipes and so here I am doing that.

[github-actions]

To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks!

[sbillinge]

@conda-forge-admin, please ping @conda-forge/help-python-c, ready for review!

Thanks so much

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-webservice.

I was asked to ping @conda-forge/help-python-c, and so here I am doing that.