Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Script locations #1

Open
Leont opened this issue Jul 5, 2015 · 9 comments
Open

Script locations #1

Leont opened this issue Jul 5, 2015 · 9 comments

Comments

@Leont
Copy link
Member

Leont commented Jul 5, 2015

Currently only script/ is described, should it also cover bin/?

@skaji
Copy link

skaji commented Dec 13, 2015

@haarg
Copy link
Member

haarg commented Mar 6, 2017

I would strongly support installing scripts from bin. Using bin for this seems much more common.

@Leont
Copy link
Member Author

Leont commented Mar 17, 2017

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.

@miyagawa
Copy link
Member

miyagawa commented Apr 22, 2018

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.

@haarg
Copy link
Member

haarg commented Apr 22, 2018

If my choices are putting scripts in scripts/ or not using static install, I'll pick not using static install.

@Leont
Copy link
Member Author

Leont commented Apr 22, 2018

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)

@miyagawa
Copy link
Member

@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

@miyagawa
Copy link
Member

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

@miyagawa
Copy link
Member

miyagawa commented Apr 22, 2018

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants