[Bioperl-l] bioperl executables files and dist-zilla
Fields, Christopher J
cjfields at illinois.edu
Fri Jan 9 17:12:47 UTC 2015
I think in bioperl-live much of the script munging during build/install is handled by the Module::Build sub-class (Bio::Root::Build) but is a bit of a hack; yeah this needs to be migrated to dzil. Looking at  it appears in the role that the directory is settable via the ‘dir’ attribute; would this also be settable during configuration? The plugin consuming the role is Dist::Zilla::Plugin::ExecDir
Alternatively you could move scripts -> bin and symlink ‘scripts’ to point to the new location but I’m not sure how well git handles symlniks. IIRC it sometimes tries to resolve them.
Re: extensions, I wouldn’t have a problem with this except that old installations of the scripts would still be around, correct? If so, we would need to add a bit of code that checks for the presence of old versions and removes/replaces them. Might be more trouble than it’s worth.
On Jan 8, 2015, at 6:04 PM, Carnë Draug <carandraug+dev at gmail.com> wrote:
> when installing new bioperl modules with dist zilla, the executable files
> are not being installed. The reason is that our dist zilla plugin bundle 
> is searching for them in the default directory "bin/" while bioperl seems
> to have them in a "scripts/" directory. This is done by the ExecFiles plugin.
> I can change this easily or I can just move the binaries to "bin/" (which
> I think is more common). Also, dropping the file extensions would make
> things simpler.
> One last thing, I was thinking of adding the SetScriptShebang plugin 
> to the bundle. Opinions?
>  https://metacpan.org/pod/Pod::Weaver::PluginBundle::BioPerl
>  https://metacpan.org/pod/Dist::Zilla::Role::ExecFiles
>  https://metacpan.org/pod/Dist::Zilla::Plugin::SetScriptShebang
> Bioperl-l mailing list
> Bioperl-l at mailman.open-bio.org
More information about the Bioperl-l