Replies: 1 comment
-
|
@dyoshikawa would love your sign off on this, too. And same question. Can this be the default behavior or would you like a flag to enable it? And how do you feel about a flag to copy these into a different location (that is presumably on the PATH)? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
We're using rulesync pretty extensively in our setup. It's awesome!
However, we want to be able to provide executables (scripts) in our skills packages. I could totally be missing something but it looks like rulesync strips that, both in the install as well as the generate.
I fully understand that executables in skills can be a security concern but if we make them executable, it's for a reason. I'd love for this to either be the default or at least have an option to enable it in the config.
If people are good with either of these options, I'm happy to code it up.
Also, it would be nice to have an easy way to put executables from skills on the PATH. I'm thinking we could have a new config value (e.g.
copySkillExecutablesToDir) that would be used in the skill generation logic (for installed, fetched, local, and global skills) to identity executables and then copy them into the provide directory (which would presumably be on the PATH).Thoughts?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions