Hi Steve, It is very nice to hear a confirmation from you that you and others in this network are carrying the torch and are committed to maintaining this great tool set.
Since I am new here, let me tell you what we're doing. We have been developing a freeware tool <http://irp.nih.gov/our-research/accomplishments/procedures/procedures-and-therapies/nlm-scrubber-paving-the-road-to-big-data-by-securing-patient-privacy> whose user base is clinical scientists. Currently, our tool has a command line interface and requires an ASCII configuration file to be edited. Other comparable software packages are either commercial and very expensive or freeware like ours but require a lot of overhead (installing a bunch of other software packages plus licensing plus maintenance). We want to keep ours as simple as possible so that it can be used by every clinical scientist who wants to do research using clinical reports without breaching patient privacy. For this reason, we chose ActiveState, of which PDK enables us to wrap everything into a single executable package, available on three common platforms (Win, Linux, Mac). Given that we are a very small group of developers under a huge organization, we also try things easier at our end and when necessary pay some premium for it. Up to this point, we have not installed any CPAN packages manually, rather we waited for ActiveState to test them and make them available via PPM, their Perl package manager. This way we do not have to deal with package dependencies and their maintenance. We provide Mac version of our software in order to reach clinical scientists who are most familiar with Mac or work in Mac environment only, but we are not as familiar with Mac environment as we are with Linux and to some extent with Windows. So, long story short, we have not tried to install any Wx package and do not plan to do so until they are available by ActiveState for all three platforms. ActiveState attempts failed in all three accounts, two of which are related to their timeout windows <https://community.activestate.com/node/18630>. And one of them (Windows version) could not be installed due to an issue related to Alien::wxWidgets, but I just saw that that particular issue has apparently been resolved and Windows version is right now available <http://code.activestate.com/ppm/Wx/?_ga=1.65076974.1131807206.1451921858>. Hooray! Since at least one version is working, I hope ActiveState would extend the timeout window in order to make the other two versions would work as well. Thank you, --mehmet PS. I will keep you posted if and when ActiveState tests Mac and Linux packages with extended timeout window. PPS. I am moving my post from (Re: wxPerl Infrastructure Support Issues) to the current thread so that your infrastructure discussion would not be hijacked by this. On Wed, Jan 13, 2016 at 2:31 AM, Steve Cookson - gmail < steveco.1...@gmail.com> wrote: > Hi Mehmet, > > Thanks for your email. > > James' list does indeed look intimidating, but I hope once we start the > momentum will build. > > Wx and Alien::Widgets are not abandoned, they are just under-resourced. > > Here is a list of recent updates at sourceforge: > > http://sourceforge.net/p/wxperl/code/HEAD/tree/ > > We here are all the maintainers. If we don't like something we fix it in > our own environments and post it here. Mark will migrate it to the various > repositories. > > We have had almost as much activity on the list in January 2016 than in > the whole of 2015. Long may it continue! > > I don't have a Mac, but maybe I can help you with your installation > problems. Are you still getting the same error? Ie "No wxWidgets build > found.". > > Please remind us how you are installing. The purpose of Alien::wxWidgets > is to install wxWidgets in a selected directory and then point wxPerl to > it. There is normally a configuration file or environment variable that > will point wxPerl (ie Wx) to the right directory. > > Please post your current status and I'll try to help you. > > Regards > > Steve. > > > On 12/01/16 17:53, Mehmet Kayaalp wrote: > > On Fri, Jan 8, 2016 at 8:04 PM, James Lynes <jmlyne...@gmail.com> wrote: > [...] > > wxPerl Language Support > > Bug Fixes(Mark & ?) > > I was looking for a proper pigeon hole to place my support request wrt > wxPerl for Win-64 on ActivePerl > <http://www.nntp.perl.org/group/perl.wxperl.users/2016/01/msg9577.html>. > On the main wiki page, I found links to two support pages, Wx > <https://rt.cpan.org/Public/Dist/Display.html?Name=Wx> and > Alien::wxWidgets > <https://rt.cpan.org/Public/Dist/Display.html?Name=Alien-wxWidgets>, at > cpan, but they are not maintained. > > 41678 <https://rt.cpan.org/Ticket/Display.html?id=41678> *Can't build on > OpenBSD perl 5.10 wxWidgets 2.8.7 > <https://rt.cpan.org/Ticket/Display.html?id=41678>* open Critical 6 years > ago 0.40 > 0.41 > 0.42 Maintainers of both sites are listed as MBARBON > <https://rt.cpan.org/Public/Dist/ByMaintainer.html?Name=MBARBON>, and > MDOOTSON <https://rt.cpan.org/Public/Dist/ByMaintainer.html?Name=MDOOTSON> > . > Clearly they abandoned the effort, or that is the impression I get from > outside. > Does anyone willing to take responsibility to maintain these pages? > > As I understand from you discussions, there is a new on-going reformation > attempt. > James' list is a good plan but it also seems overwhelming to approach, > unless there is a prioritization in place. > I would suggest assigning a high priority to making the existing software > work on the current platforms with the latest versions of Perl/ActivePerl. > > My two cents. > > >
