forcing older perl to use an older version of cpan module?

[Chia-liang Kao <clkao@bestpractical.com>]

Hi,

So I uploaded new B::Utils, and found out it didn't compile on 5.6.2,  
which is fixable with ppport.h.  However since the module is now also  
providing some c function for other xs modules, it is itself an xs  
module.  The dynaloader on 5.6.2 appears not to handle dl_load_flags  
well (at least on darwin), so the tests still fail.

I am wondering if there is a way in meta.yml or some places to note  
that B::Utils 0.05 is the latest supported version if you are on perl  
5.6.  In this particular case we can of course move the xs bits into  
another module, but i think the other maintainers of b::utils agreeed  
it makes sense to have the new stuff in the module.  I am sure there'd  
be other other modules with the same situation where since a certain  
version it requires 5.8.

In other words, to do module development that is only for newer perl  
without breaking people who are still using 5.6, what's the best way  
for this and how do we handle this gracefully?

Cheers,
CLK

---

Follow-Ups from:

Moritz Lenz <moritz@casella.verplant.org>

---

[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index][Thread Index][Top&Search][Original]

---