Hello, I just started smoke testing Citrus perl today; I'm not sure but if you can get it working on your system then you should be able to repackage it. http://www.citrusperl.com/ - citrusperl claims to have a repackaging tool; I haven't used it yet. would be interested in hearing your results.
pretty cool that I happened across this google group on the day you posted an email to this group when the last email to the group was on 11/30/13! (I'm also cross posting to cpan-testers-discuss@perl.org since my issues are related to metabase_id.json and smoke testing) I was able to get the report up to the server but sadly I had issues again with getting the proper metabase_id.json to get read and saved by the cpan client. I am using multiple versions of perl on my machines and would like to be able to change a few environment variables and fire up cpan from different portable paths. thought I'd give citrus perl a try. placing it in root so I'm sitting in C:\citrusperl-standard-51603-msw-x64-018\perl\bin I also tried setting the APPDATA env as suggested in http://wiki.cpantesters.org/wiki/YACSmokePOE c:\citrusperl-standard-51603-msw-x64-018\perl\bin>set APPDATA=C:\citrusperl-standard-51603-msw-x64-018\ (is is hopefully helping to place the cpan metadata relative to where I want it, not the strawberry perl data on disk already) But, first off, for some reason the config.pm file comes down readonly. which gives you this mixed slash path...clearing the read only and it fixed that. cpan[6]> o conf commit Your C:\citrusperl-standard-51603-msw-x64-018\perl\vendor\lib/CPAN/Config.pm file is not writable. I will attempt to write your configuration to C:\Users\dhorner\AppData\Local\.cpan\CPAN\MyConfig.pm instead. ====== Old configuration file C:\Users\dhorner\AppData\Local\.cpan\CPAN\MyConfig.pm moved to C:\Users\dhorner\AppData\Local\.cpan\CPAN\MyConfig.pm.bak commit: wrote 'C:\Users\dhorner\AppData\Local\.cpan\CPAN\MyConfig.pm' ==== So then moving on to the reporting and transport.... o conf init test_report as suggested by http://wiki.cpantesters.org/wiki/TestDuringInstall >(Recommended: 'Metabase uri https://metabase.cpantesters.org/api/v1/ id_file metabase_id.json') >transport? [Metabase uri https://metabase.cpantesters.org/api/v1/ id_file C:\citrusperl-standard-516 03-msw-x64-018\perl\cpan\prefs\metabase_id.json] I set the full path to the metabase_id.json in the transport URI cause I wanted to be sure on where it was....then I saw the following sad path in the output: CPAN::Reporter: writing config file to 'C:\strawberry-perl-5.20.0.1-64bit-PDL\data\.cpanreporter\con fig.ini'. Returning to CPAN configuration. commit: wrote 'C:\citrusperl-standard-51603-msw-x64-018\perl\vendor\lib/CPAN/Config.pm' So citrusperl knows to write the config.pm in the right place, but for some reason it isn't respecting the APPDATA and it somehow gets C:\strawberry-perl-5.20.0.1-64bit-PDL\data\ as the proper place to house .cpanreporter.... which is WRONG. citrus perl shouldn't take it personal though; http://www.nntp.perl.org/group/perl.beginners/2014/09/msg124753.html http://www.nntp.perl.org/group/perl.cpan.testers.discuss/2014/07/msg3453.html things require care and maintenance. thanks, --dave http://dave.thehorners.com/tech-talk/programming/94-perl-programming http://dave.thehorners.com/tech-talk/programming/510-perl-cpan-packaging-notes On Wednesday, September 3, 2014 3:37:25 PM UTC-4, grodid wrote: > > Hi Mark, > > As the title says : is there a chance to get the (rather) new 3.0.1 or > 3.1.0 version of wxWidgets packaged together with Citrus Perl , please ? > I am currently working with Mac OS X 10.9.3 (64 bits). > > Thanks in advance for any hints, Regards, G. >
