tech-pkg archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: m4 and after (was: Yacc Shaving)
On 03/12, Amitai Schleier wrote:
> So my question in the previous boils down to, should I look for all
> occurrences of USE_TOOLS+=auto* and make sure gm4 is in those USE_TOOLS
> lists? Or would it match more people's expectations if USE_TOOLS+=autoconf
> were to automatically imply USE_TOOLS+=gm4? I'm guessing you'd been leaning
> toward the latter; does this explanation do anything to solidify or change
> what folks would expect here?
Hi, Amitai!
This still doesn't make sense to me. You said that if you install
autoconf, you get its runtime dependencies too, which presumably
includes gm4. So, why would you be talking here about adding an
explicit gm4 to USE_TOOLS for the case where autoconf is already in
USE_TOOLS? Are you saying that USE_TOOLS works differently than a
normal package install in that only the tool installed via USE_TOOLS
gets put at the front of pkgsrc's internal PATH, *not* any of its
dependencies? Is that the difference?
Thanks,
Lewis
- References:
- Yacc Shaving, or, Latest macOS CLT Laccs Something
- Re: Yacc Shaving, or, Latest macOS CLT Laccs Something
- Re: Yacc Shaving, or, Latest macOS CLT Laccs Something
- Re: Yacc Shaving, or, Latest macOS CLT Laccs Something
- Re: Yacc Shaving, or, Latest macOS CLT Laccs Something
- Re: Yacc Shaving, or, Latest macOS CLT Laccs Something
- m4 and after (was: Yacc Shaving)
- Re: m4 and after (was: Yacc Shaving)
- Re: m4 and after (was: Yacc Shaving)
Home |
Main Index |
Thread Index |
Old Index