ENH added alsa-lib-cos7-ppc64le

[beckermr]

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

[conda-forge-linter]

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/alsa-lib-cos7-ppc64le) and found some lint.

Here's what I've got...

For recipes/alsa-lib-cos7-ppc64le:

• The top level meta keys are in an unexpected order. Expecting ['package', 'source', 'build', 'test', 'outputs', 'extra'].
• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have a build/number section.
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• The outputs section contained an unexpected subsection name. noarch is not a valid subsection name.