<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi, I update the help2man port recently to default to perl 5.38. <div><br></div><div> Thanks,</div><div> Kurt<br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Nov 6, 2024, at 10:19 AM, Ryan Carsten Schmidt <ryandesign@macports.org> wrote:</div><br class="Apple-interchange-newline"><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div dir="auto"><div dir="ltr"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div dir="ltr"></div><div dir="ltr">On Nov 5, 2024, at 03:23, Maxim Abalenkov wrote:</div><div dir="ltr"><blockquote type="cite"><br></blockquote></div><blockquote type="cite"><div dir="ltr">I recently ran into trouble with a command-line tool called ‘help2man’:<div><br></div><div><div>HELP2MAN starpu_env.1</div><div>Encode.c: loadable library and perl binaries are mismatched (got handshake key 0x10200080, needed 0xfb80080)</div></div><div><br></div><div>I assume, this happens because I have multiple Perl installations on my system: Apple’s, MacPorts’ and my own compiled from source.</div></div></blockquote><div><br></div>It should not be a problem to have as many different perls installed as you like; they are designed not to interfere with one another. <div><br></div><div>You should file a bug report for the help2man problem you encountered, assuming a ticket does not already exist for this. Since it has variants for different perls, it should be using the perl you chose; if it doesn't, that's a bug. <br><div><br></div><br><blockquote type="cite"><div dir="ltr"><div>When I look at all possible port variants for help2man I see:</div><div><br></div><div><div>sudo port variants help2man</div><div>Password:</div><div>help2man has the variants:</div><div> perl5_28: Use MacPorts perl5.28</div><div> * conflicts with perl5_30 perl5_32 perl5_34 perl5_36 perl5_38</div><div> perl5_30: Use MacPorts perl5.30</div><div> * conflicts with perl5_28 perl5_32 perl5_34 perl5_36 perl5_38</div><div> perl5_32: Use MacPorts perl5.32</div><div> * conflicts with perl5_28 perl5_30 perl5_34 perl5_36 perl5_38</div><div>[+]perl5_34: Use MacPorts perl5.34</div><div> * conflicts with perl5_28 perl5_30 perl5_32 perl5_36 perl5_38</div><div> perl5_36: Use MacPorts perl5.36</div><div> * conflicts with perl5_28 perl5_30 perl5_32 perl5_34 perl5_38</div><div> perl5_38: Use MacPorts perl5.38</div><div> * conflicts with perl5_28 perl5_30 perl5_32 perl5_34 perl5_36</div><div> universal: Build for multiple architectures</div></div><div><br></div><div>Would it be possible to provide another help2man variant that would use perl5_40?</div><div><br></div><div>This brings me to a more general question. Is one version of perl5_XY enough to power all other MacPorts that depend on a Perl port or do we really need perl5_34 for one port A and perl5_36 for another port B? Is it possible to bring ‘law and order’ into a MacPorts installation and say: “Dear ports, please use the one and only Perl port v5.40?”</div></div></blockquote><br></div><div>Ports that use perl should either depend on the perl5 port (if they don't care about the perl version and don't use any modules) or the perl5.34 port (if they require a more recent perl or they require any perl modules). </div><div><br></div><div>We cannot move MacPorts to a newer default version of perl than 5.34 until someone contributes module ports for the newer perls. See <a href="https://trac.macports.org/ticket/67830">https://trac.macports.org/ticket/67830</a></div><div><br></div><div>It looks like help2man depends on p5-locale-gettext and someone has already contributed perl 5.36 and 5.38 versions of just that module so variants for those versions of perl could be added to the help2man port. </div><div><br></div></div></div></div></blockquote></div><br></div></body></html>