BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] perl/Tk
- Subject: [Discuss] perl/Tk
- From: bill.n1vux at gmail.com (Bill Ricker)
- Date: Fri, 27 Feb 2015 18:11:11 -0500
- In-reply-to: <BN3PR0401MB1204046737D3F170718EE3ABDC150@BN3PR0401MB1204.namprd04.prod.outlook.com>
- References: <20150227192654.GA27874@aldeberon> <BN3PR0401MB1204046737D3F170718EE3ABDC150@BN3PR0401MB1204.namprd04.prod.outlook.com>
Ignoring Ned's inflammatory rant, he has a kernel of sense - > if you can abandon cpan, and use packages that are built in to your yum repository. As a Perl pro, i agree with this much with Ned's rant -- this is very good advice for C-based binary extensions (including library wrappers such as Tk), when the Perl it's to be used with is from OS Yum/Deb/... repo originally. You really really want all the C files built with the same toolchain and flags, and a single build system is easiest way there. [ If you build your own Perl from sources (not very hard really), building from CPAN works fine with it. If one is going to have lots of custom built modules, having a local perl is recommended, if only to avoid a sys upgrade updating /bin/perl and obsoleting all your local built modules ! For pure-Perl modules - without C/lib* dependencies - building from CPAN works fine. ] -- Bill Ricker bill.n1vux at gmail.com https://www.linkedin.com/in/n1vux
- References:
- [Discuss] perl/Tk
- From: jdm at moylan.us (dan moylan)
- [Discuss] perl/Tk
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- [Discuss] perl/Tk
- Prev by Date: [Discuss] perl/Tk
- Next by Date: [Discuss] perl/Tk
- Previous by thread: [Discuss] perl/Tk
- Next by thread: [Discuss] perl/Tk
- Index(es):