Open Leont opened 9 years ago
I would strongly support installing scripts from bin. Using bin for this seems much more common.
My main reason for using script was that perl's own install infrastructure distinguishes between script and bin install location (and hence has a blib/bin
and a blib/script
. I know of only two distributions that use blib/bin
though, this distinction is mostly theoretical.
i don't have a strong opinion on this. Since this is a new protocol, supporting script
sounds fine as a starter to me. Module authors who want to use static_install can have a dzil plugin or some sort that puts/moves the executables from bin
to script
in release time, for example.
If my choices are putting scripts in scripts/
or not using static install, I'll pick not using static install.
Given a number of people have asked for this, I'm leaning towards adding this (even if I'm not so fond of it myself)
@haarg can you clarify the reason? do you strongly prefer having bin
in your git repo?
BTW, this might be something that we want extra configurations for, and maybe easier if we turn x_static_install
to be a hash? Is that too complicated or too late?
x_static_install:
version: 1
bindir: bin
Rubygems default template has switched away from bin
to exe
but it sounds like for an entirely different silly reason http://bundler.io/blog/2015/03/20/moving-bins-to-exe.html
I'm totally fine with supporting both bin
and script
btw. What should be the behavior if there're the files with the same name in both directories? Maybe prefer script
that way?
Currently only
script/
is described, should it also coverbin/
?