-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add ability to pick which script is installed if repo provides multiple #18
Comments
Thanks for creating this issue. It's definitely something I've had in mind while building the initial version, even though I had to leave it out. Right now we assume there is only one entry in What should happen if a lib has multiple scripts in What about providing a default script to install when there are multiple? Should this be supported? Perhaps a lib author could add a key in the script config such as |
Yeah, I think having a
That also makes me think that there could be a way of discovering what scripts are available. Perhaps:
That way the above "default" message can include a hint about running with
Now that I reflect back on writing all of that, I think that perhaps the |
I also have the same setup at https://github.com/logseq/bb-tasks though I'm wanting to install all my scripts at once. Since :bbin/bin is a map, I thought I could do something in bb.edn like: :bbin/bin
{logseq-import {:main-opts ["-m" "logseq.bb-tasks.bin.logseq-import/-main"]
logseq-export {:main-opts ["-m" "logseq.bb-tasks.bin.logseq-export/-main"]} When it only picked the first one I thought it was a bug until I found this issue. If this is unrelated enough, I could open a separate issue. Thanks for the great tool! |
Awesome project, thanks for creating it! I tried it out and everything is working so far.
I have a repo containing multiple babashka scripts, each with its own main.
For now, I need to specify the main opts and the script name on the
bbin
install line, like this:Since the
:bbin/bin
value in the repo'sbb.edn
file is a map, how about supporting a way of picking which script is installed? Something like this:It could even be extended to support an
:all
keyword to install all scripts found.Thanks again.
The text was updated successfully, but these errors were encountered: