Re^4: Business::WorldPay::Junior and last release date

Thanks Renne.

I e-mailed him just after my initial post. I'll reply with a summary.

Are you, or anyone else aware of any similar "Charge for" CPAN module? I have not seen this before.

Gavin.

Walking the road to enlightenment... I found a penguin and a camel on the way.....
Fancy a yourname@perl.me.uk? Just ask!!!

Comment on Re^4: Business::WorldPay::Junior and last release date

Replies are listed 'Best First'.
Re^5: Business::WorldPay::Junior and last release date by CountZero (Bishop) on Dec 27, 2005 at 17:00 UTC
The CPAN module is free, but the newer version (which is not on CPAN) seems not. Once you put something on CPAN it is up for grabs although technically and legally you could insist on a licence more restrictive than the usual ones. How you would be able to enforce that is something else of course. Since CPAN is all source-code, any "clever" locks made by the author could be unlocked by an other Perl-coder. CountZero "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law	[reply]
Re^6: Business::WorldPay::Junior and last release date by ghenry (Vicar) on Dec 28, 2005 at 09:36 UTC
I got this reply: On Tue, 27 Dec 2005, Gavin Henry wrote: > Is your module still maintained and is there still a charge for it? > > Does it still need Mysql, as we prefer Postgresql. Gavin, As I no longer use WorldPay I am not actively maintaining the module however it does still work. The charge was only ever levied for downloads direct from my website and nobody ever paid it as the module is available from CPAN without charge. Somebody did suggest he was going to patch the module to support postgresql however he never did so. As I don't use postgresql I haven't done the job either. The code isn't obtuse so you should be able to make the changes yourself if you wish to. Jason Clifford Answers it all then ;-) Walking the road to enlightenment... I found a penguin and a camel on the way..... Fancy a yourname@perl.me.uk? Just ask!!!	[reply]