Skip to content
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

Closed

Conversation

mitchblank
Copy link
Contributor

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 specify INSTALLDIRS=vendor when you build it that's what you get. Maybe the default INSTALLDIRS changed at some point and broke this formula?

cc @zachauten @mistydemeo

@BrewTestBot BrewTestBot added the missing license Formula has a missing license which should be added label Dec 6, 2020
@Leont
Copy link

Leont commented Dec 7, 2020

In general, this is why you don't why you do not want to be using PREFIX=. It does a substitution based on the default installation paths for the current value of INSTALLDIRS. That means that the resulting paths will be different for different configurations of perl (and obviously different values of INSTALLDIRS).

I would highly recommend using INSTALL_BASE instead of PREFIX, that will result in a much more predictable end-result.

@mitchblank mitchblank force-pushed the pod2man-change-install-location branch from bfef573 to b21a379 Compare December 27, 2020 20:59
@chenrui333 chenrui333 mentioned this pull request Dec 28, 2020
5 tasks
@chenrui333 chenrui333 added the CI-force-arm [DEPRECATED] Don't pass --skip-unbottled-arm to brew test-bot. label Dec 28, 2020
@chenrui333
Copy link
Member

@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.
@mitchblank mitchblank force-pushed the pod2man-change-install-location branch from b21a379 to 6d7d219 Compare December 28, 2020 04:17
@carlocab
Copy link
Member

greping the source tarball shows

license any_of: ["GPL-1.0-or-later", "Artistic-1.0-Perl"]

Don't update this PR, though, as CI is fully backed up with revision bumps. It can wait till this one is merged.

Copy link
Member

@carlocab carlocab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @mitchblank!

@BrewTestBot
Copy link
Member

🤖 A scheduled task has triggered a merge.

@BrewTestBot BrewTestBot added the outdated PR was locked due to age label Jan 29, 2021
@Homebrew Homebrew locked as resolved and limited conversation to collaborators Jan 29, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
CI-force-arm [DEPRECATED] Don't pass --skip-unbottled-arm to brew test-bot. missing license Formula has a missing license which should be added outdated PR was locked due to age
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants