giflib 5.2.2

[BobbyVillaluz]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

• Update giflib formula to version 5.2.2. Fixed the build failures (caused by inadvertent whitespace modifications) which blocked Homebrew/homebrew-core#163204.
• Remove previous Makefile patch, based on this comment
• Add doc Makefile patch which moves the giflib-logo.gif target from the allhtml prerequisites to the website prerequisites, so that ImageMagick is not required to build the giflib package
• Add MIT license, matching that of the giflib entry in Arch Linux package repository
• Credit to @miccal and @chenrui333 for the original PR (#163204)

[github-actions]

Thanks for contributing to Homebrew! 🎉 It looks like you're having trouble with a CI failure. See our contribution guide for help. You may be most interested in the section on dealing with CI failures. You can find the CI logs in the Checks tab of your pull request.

[BobbyVillaluz]

@SMillerDev does the CI-long-timeout label need to be re-added to allow the checks to pass? It looks like I don't have permission to merge the PR manually.

Error: PR requires the CI-long-timeout label but it is not set!
Error: If the longer timeout is not required, remove the "long build" label.
Error: Otherwise, add the "CI-long-timeout" label.
Error: No more than 2 PRs at a time may use "CI-long-timeout".

[bevanjkay]

@BobbyVillaluz The label has to be managed manually by maintainers at the moment, as we only have CI availability to run two long builds concurrently. It will be kicked off when there's space.

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.