Name conflict for sash

Create issue
Issue #37 resolved
Former user created an issue

Hi, packaging the Sagittarius for Archlinux, a consistency tool complained about the missing dependency of "sash" on the generated binary. After I investigated the issue, I think there is a conflict for the name of the Sagittarius shell and the stand-alone shell (https://en.wikipedia.org/wiki/Stand-alone_shell). Maybe you can rename the sagittarius shell in "sarepl" or simply "sagittarius" (as others scheme's implementations: kawa, guile, racket)

Comments (2)

  1. Takashi Kato repo owner

    Thank you for the report!

    I've never heard about other 'sash'. Removing the current name would cost a lot for existing scripts (mostly for my sake, though). So what I can think of is that change 'sash' to 'sagittarius' then make a symbolic link named 'sash'. Would this work on Archlinux's package system?

  2. Takashi Kato repo owner

    Renamed shell executable file name to sagittarius. (Fixes #37) The legacy sash is kept as above file's symbolic link. On Windows, nothing has been changed (keep sash as it is).

    → <<cset 06b69dd9062d>>

  3. Log in to comment