Add recipe for SFCGAL 2.0.0

[lbartoletti]

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.

[github-actions]

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

File-specific lints and/or hints:

• recipes/sfcgal/meta.yaml:
  • lints:
    • The following maintainers have not yet confirmed that they are willing to be listed here: <votre_nom_d'utilisateur_github>. 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 wanted to let you know that I linted all conda-recipes in your PR (recipes/sfcgal/meta.yaml) and found some lint.

Here's what I've got...

For recipes/sfcgal/meta.yaml:

• ❌ There are 1 too many lines. There should be one empty line at the end of the file.

For recipes/sfcgal/meta.yaml:

• ℹ️ The boost-cpp output has been superseded by libboost-devel (as of 1.82), which now comes with a run-export (on libboost) as well. In case you only needed the boost headers, you should use libboost-headers.

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

[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/sfcgal/meta.yaml) and found it was in an excellent condition.

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

For recipes/sfcgal/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/13011595024. Examine the logs at this URL for more detail.}

[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/sfcgal/meta.yaml) and found it was in an excellent condition.

[conda-forge-admin]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipes/sfcgal/meta.yaml) and found some lint.

Here's what I've got...

For recipes/sfcgal/meta.yaml:

• ❌ The "outputs" section was expected to be a list, but got a ruamel.yaml.comments.CommentedMap.
• ❌ The top level meta keys are in an unexpected order. Expecting ['package', 'source', 'build', 'requirements', 'test', 'outputs', 'about', 'extra'].
• ❌ The "outputs" section was expected to be a list, but got a ruamel.yaml.comments.CommentedMap.
• ❌ The "outputs" section was expected to be a list, but got a ruamel.yaml.comments.CommentedMap.
• ❌ The "outputs" section was expected to be a list, but got a ruamel.yaml.comments.CommentedMap.

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

[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/sfcgal/meta.yaml) and found it was in an excellent condition.

[conda-forge-admin]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipes/sfcgal/meta.yaml) and found some lint.

Here's what I've got...

For recipes/sfcgal/meta.yaml:

• ❌ Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [39]

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

[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/sfcgal/meta.yaml) and found it was in an excellent condition.