Adding cb-clipboard

[eunos-1128]

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 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.

_{This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11298249757.}

[eunos-1128]

@Slackadays

Could you agree to being one of the maintainers for this conda package as Clipborad author?

I want to make this great software available across platforms also using conda packaging system.

[Slackadays]

I can be one of the maintainers

[eunos-1128]

I can be one of the maintainers

Thank you!

[eunos-1128]

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

[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.

_{This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11315889697.}

[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/cb-clipboard/recipe.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/cb-clipboard/meta.yaml) and found some lint.

Here's what I've got...

For recipes/cb-clipboard/meta.yaml:

• The "test" section was expected to be a dictionary, but got a CommentedSeq.
• The recipe must have some tests.
• The "test" section was expected to be a dictionary, but got a CommentedSeq.

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

[eunos-1128]

I replaced recipe.yaml with meta.yaml to use conda-build instead of rattler-build because MacOS build always fails even with the config file defining c_stdlib_version.

prefix-dev/rattler-build#1117

[Slackadays]

@xhochy The fixes have been implemented