Provide a linter hint for xorg-proto packages

[hmaarrfk]

@pkgw I think this is not the ideal way, but we have been using the newer proto on some new recipes and I am noticing clobbering in a few environments. I think it would be fine to use this in lieu of a more complicated migration

Let me know what you think

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

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

[hmaarrfk]

Kind ping @pkgw

[pkgw]

@hmaarrfk Sorry for being very slow to respond here. This seems like a fine start. There are of course many many other proto packages that could also be mentioned here, but Xext seems like one of the more common offenders. Maybe it would be good to also have a record for xorg-xproto, mainly because it seems like that one might be confusing for people due to the naming similarity.

[hmaarrfk]

awesome. I just duplicated the message for both, and we'll see what happens over time.

[conda-forge-admin]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• github-actions: passed

Thus the PR was passing and merged! Have a great day!

[jakirkham]

Started a discussion about a migrator for this case: regro/cf-scripts#3360

[jakirkham]

Expanded this to include all xorg-*protos in PR: #6816

Please let me know what you think 🙂