-
-
Notifications
You must be signed in to change notification settings - Fork 12.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pod2man: change install location inside keg #66367
pod2man: change install location inside keg #66367
Conversation
In general, this is why you don't why you do not want to be using I would highly recommend using |
bfef573
to
b21a379
Compare
@mitchblank can you do a rebase to trigger the arm build? Thanks! |
As discussed with Homebrew#66370 (comment) Big Sur's system perl changed how "PREFIX=" is treated as an install destination. The more explicit way to control MakeMaker is to set INSTALL_BASE instead, which should result in consistent behavior between different OS/X versions.
b21a379
to
6d7d219
Compare
Don't update this PR, though, as CI is fully backed up with revision bumps. It can wait till this one is merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @mitchblank!
🤖 A scheduled task has triggered a merge. |
Investigating recent bottling failures and found that pod2man was failing due to
brew test
failing. The issue is that the test assumes that this (keg-only) formula installed its binary as.../Cellar/pod2man/4.14/bin/pod2text
but it was actually ending up at:
.../Cellar/pod2man/4.14/local/bin/pod2text
I'm going to assume that
brew test
worked at some point and that the former is the correct place to install it. Hopefully I'm right about that; I am no perl expert. It seems that if you specifyINSTALLDIRS=vendor
when you build it that's what you get. Maybe the defaultINSTALLDIRS
changed at some point and broke this formula?cc @zachauten @mistydemeo