Re: local packages in windows

In general, you don't necessarily have to install .pm files (or even their associated .dll files, if any) to be able to run scripts), Perl just has to be able to find them.

In my experience, most scripts that come with .pm files are able to locate their "private" .pm files on their one, as long as you either unzip/unpack them, then run the script from that location, or you put the .pm files (and .dll files, if any) in the same folder as the script.

Comment on Re: local packages in windows

Replies are listed 'Best First'.
Re^2: local packages in windows by Arthfael (Initiate) on Jul 11, 2014 at 18:14 UTC
OK, thanks guys. I checked and indeed I had not installed BioPerl. However, even after installing it the output is unchanged: I get files with the headers I would be expecting to get based on the associated publication, but no content under the headers. About the Excel-corrupted file: I have made a fixed version. I will never understand why Microsoft does not want to fix this. It's so annoying when protein Sep7 randomly turns into September 7!	[reply]
Re^3: local packages in windows by Arthfael (Initiate) on Jul 15, 2014 at 15:49 UTC
Hi monks, Sorry to bother you guys again but my issue hasn't been resolved. I have checked and while all the necessary packages are now installed, the script still only produces empty headers as output. I have tried contacting the script maker but since it dates from 2007 he may not reply. Any idea why the script is failing?	[reply]
Re^4: local packages in windows by marto (Cardinal) on Jul 15, 2014 at 16:13 UTC
I very briefly looked at this script, and don't remember liking what I saw (not a lot of error checking going on). I also don't have any input to test this with. I can only suggest you debug this script if you want to use it. Failing that perhaps there is something in BioPerl which does the same thing this script is supposed to. Tutorials->Basic debugging checklist.	[reply]