The BioPerl distribution is famously finicky to install. Notably, many modules can fail to install based on one out of a few hundred (or thousand) tests failing, in which case it is very common to use --force to proceed with installation anyways. The BioPerl project itself recommends that users of the distribution specify exactly which modules they need rather than saying "install BioPerl":
[...] the BioPerl distribution only includes a subset of the project modules. Because of this, the meaning of "installing BioPerl" is rarely clear. Instead of "install BioPerl", the aim must be "install module X".
As of version 1.14.6 prokka seems to only need the following BioPerl modules:
Prokka could probably simplify its installation steps by specifying exactly these modules. I'm installing Prokka in a cluster setup with applications on network-based shared storage and I'm doing the following:
The BioPerl distribution is famously finicky to install. Notably, many modules can fail to install based on one out of a few hundred (or thousand) tests failing, in which case it is very common to use
--force
to proceed with installation anyways. The BioPerl project itself recommends that users of the distribution specify exactly which modules they need rather than saying "install BioPerl":As of version 1.14.6 prokka seems to only need the following BioPerl modules:
Prokka could probably simplify its installation steps by specifying exactly these modules. I'm installing Prokka in a cluster setup with applications on network-based shared storage and I'm doing the following:
Incidentally I still had to use
--force
to get these to install in my environment. Hmmm.