Create xorg-libxshmfence feedstock

[ehfd]

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.

Corresponds to #26241 and conda-forge/cdt-builds#66 (comment).

[conda-forge-webservices]

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

[conda-forge-webservices]

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/xorg-libxshmfence/meta.yaml) and found some lint.

Here's what I've got...

For recipes/xorg-libxshmfence/meta.yaml:

• The source section contained an unexpected subsection name. patch is not a valid subsection name.

[conda-forge-webservices]

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

[ehfd]

@conda-forge/help-c-cpp
@conda-forge/staged-recipes

Ready for review.

This recipe replaces the libxshmfence CDTs commonly used within recipes with yum_requirements.txt, such as QT, GStreamer, etc.

@hmaarrfk @h-vetinari Could you help me out?

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