The roc executable is in the root of the nightly build. Would you consider moving it under a bin directory? This makes it easier to add to $PATH without picking up other root files (such as LICENSE).
For those unfamiliar with bin directories it is nice to have the roc executable right there, zig also does it like this. Does the picking up of other files actually cause any issues?
It pollutes the executables. For example, typing LICEN<tab will find the license file. Also if someone does have a LICENSE command that's further down the $PATH chain, the Roc one will override it (AFAIK). This behavior might be shell dependent.
I can symlink/move the roc executable to another location and add that to $PATH, it's just another step.
I suppose if other popular projects place it in root that's fine. I'm just used to a bin directory.
Yeah, we should probably move it.
Though I guess the common case for something like zig is the suggestion to symlink it into /usr/local/bin or similar
I suppose it’s more common to symlink to an existing path than add to $PATH.
I think this would be more of an issue if there were more executables (think Postgres) that you need to symlink each one separately. Since there’s just one not a problem.
There’s talk of adding roc_ls but you might not want that in $PATH anyway so makes sense to pick and choose your bins.
Last updated: Jun 16 2026 at 16:19 UTC