Rename gerbil executables to avoid installation conflict with gambit scheme #1422

New issue

2026-03-29T18:59:39Z

fcannini commented

2026-03-29 18:59:39 +00:00

(Migrated from github.com)

Hello there!

I was recently trying to install both gerbil and gambit scheme on macos using homebrew, but I was prevented by this and this.

In order to fix this conflict and help both projects, I'd like to propose to rename gerbil's executables as following:

gerbili for the interpreter
gerbilcfor the C-enabled compiler
gerbilcxx for the CXX-enabled compiler

Hello there! I was recently trying to install both gerbil and gambit scheme on macos using homebrew, but I was prevented by [this](https://github.com/Homebrew/homebrew-core/blob/main/Formula/g/gerbil-scheme.rb#L37) and [this](https://github.com/Homebrew/homebrew-core/blob/3757f70e0698f69ed93d82739bb7c962ed1c8a22/Formula/g/gambit-scheme.rb#L31). In order to fix this conflict and help both projects, I'd like to propose to rename gerbil's executables as following: - `gerbili` for the interpreter - `gerbilc`for the C-enabled compiler - `gerbilcxx` for the CXX-enabled compiler

vyzo commented

2026-03-29 19:25:17 +00:00

(Migrated from github.com)

it can be an option in configure, sure.

But there need to be some details taken care of, keep the issue open.

it can be an option in configure, sure. But there need to be some details taken care of, keep the issue open.

🎉 1

drewc commented

2026-03-30 16:14:11 +00:00

(Migrated from github.com)

Both the homebrew and our in tree brew recipes are years out of date and we
no longer conflict that way. I suggest using a modern Gerbil and not
placing any of its gambit binaries in your path. We do not conflict with
them.

Now if the year old gambit says that a 3 year old Gerbil release conflicts,
that is not really an issue to fix with a new release that does not
conflict. See the issue? Pandering to an ancient release that we wish
nobody uses to please a homebrew that nobody should use is not a good idea.

And those names you are suggesting are not what is in conflict and will not
fix that problem.

@.*** ~ % ls /opt/gerbil/bin
gxensemble gxhttpd-ensemble-test gxi gxprof gxtags
gerbil gxc gxhttpd gxhttpd-test gxpkg gxswank gxtest

As you can see, it is the gambuild-C and gsc that are in conflict. So
renaming our executables will not help in the least.

Again, rather than looking down the wrong path, I think you should use the
gcc build instructions on our MacOS readme for now, and wait for a release
that we actually endorse rather than spend your time using an outdated and
undocumented old release that nobody really uses.

We'll be releasing this year to fix that, kinda sorta. Make sense? :)

--drewc

On Sun, Mar 29, 2026 at 12:00 PM fcannini @.***> wrote:

fcannini created an issue (mighty-gerbils/gerbil#1422)
https://github.com/mighty-gerbils/gerbil/issues/1422

Hello there!

I was recently trying to install both gerbil and gambit scheme on macos
using homebrew, but I was prevented by this
https://github.com/Homebrew/homebrew-core/blob/main/Formula/g/gerbil-scheme.rb#L37
and this
https://github.com/Homebrew/homebrew-core/blob/3757f70e0698f69ed93d82739bb7c962ed1c8a22/Formula/g/gambit-scheme.rb#L31
.

In order to fix this conflict and help both projects, I'd like to propose
to rename gerbil's executables as following:

gerbili for the interpreter

gerbilcfor the C-enabled compiler

gerbilcxx for the CXX-enabled compiler

—
Reply to this email directly, view it on GitHub
https://github.com/mighty-gerbils/gerbil/issues/1422?email_source=notifications&email_token=AADVTXOHL7G74PCKD6GZO3L4TFXDFA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NBRGY2TKMRSHE4TDJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADVTXPRIUW4B7I4GKHZ2KT4TFXDFAVCNFSM6AAAAACXFGE2SCVHI2DSMVQWIX3LMV43ASLTON2WKOZUGE3DKNJSGI4TSMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Both the homebrew and our in tree brew recipes are years out of date and we no longer conflict that way. I suggest using a modern Gerbil and not placing any of its gambit binaries in your path. We do not conflict with them. Now if the year old gambit says that a 3 year old Gerbil release conflicts, that is not really an issue to fix with a new release that does not conflict. See the issue? Pandering to an ancient release that we wish nobody uses to please a homebrew that nobody should use is not a good idea. And those names you are suggesting are not what is in conflict and will not fix that problem. ***@***.*** ~ % ls /opt/gerbil/bin gxensemble gxhttpd-ensemble-test gxi gxprof gxtags gerbil gxc gxhttpd gxhttpd-test gxpkg gxswank gxtest As you can see, it is the gambuild-C and gsc that are in conflict. So renaming our executables will not help in the least. Again, rather than looking down the wrong path, I think you should use the gcc build instructions on our MacOS readme for now, and wait for a release that we actually endorse rather than spend your time using an outdated and undocumented old release that nobody really uses. We'll be releasing this year to fix that, kinda sorta. Make sense? :) --drewc On Sun, Mar 29, 2026 at 12:00 PM fcannini ***@***.***> wrote: > *fcannini* created an issue (mighty-gerbils/gerbil#1422) > <https://github.com/mighty-gerbils/gerbil/issues/1422> > > Hello there! > > I was recently trying to install both gerbil and gambit scheme on macos > using homebrew, but I was prevented by this > <https://github.com/Homebrew/homebrew-core/blob/main/Formula/g/gerbil-scheme.rb#L37> > and this > <https://github.com/Homebrew/homebrew-core/blob/3757f70e0698f69ed93d82739bb7c962ed1c8a22/Formula/g/gambit-scheme.rb#L31> > . > > In order to fix this conflict and help both projects, I'd like to propose > to rename gerbil's executables as following: > > - gerbili for the interpreter > - gerbilcfor the C-enabled compiler > - gerbilcxx for the CXX-enabled compiler > > — > Reply to this email directly, view it on GitHub > <https://github.com/mighty-gerbils/gerbil/issues/1422?email_source=notifications&email_token=AADVTXOHL7G74PCKD6GZO3L4TFXDFA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NBRGY2TKMRSHE4TDJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AADVTXPRIUW4B7I4GKHZ2KT4TFXDFAVCNFSM6AAAAACXFGE2SCVHI2DSMVQWIX3LMV43ASLTON2WKOZUGE3DKNJSGI4TSMI> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >

fcannini commented

2026-03-31 03:11:17 +00:00

(Migrated from github.com)

@drewc You have no idea how aggressive and condescending you're coming across, do you?

drewc commented

2026-03-31 16:34:56 +00:00

(Migrated from github.com)

No I do not.

On Mon, Mar 30, 2026 at 8:11 PM fcannini @.***> wrote:

fcannini left a comment (mighty-gerbils/gerbil#1422)
https://github.com/mighty-gerbils/gerbil/issues/1422#issuecomment-4159555344

@drewc https://github.com/drewc You have no idea how aggressive and
condescending you're coming across, do you?

—
Reply to this email directly, view it on GitHub
https://github.com/mighty-gerbils/gerbil/issues/1422?email_source=notifications&email_token=AADVTXJXNK36I23R2VWPCT34TMZOXA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJVHE2TKNJTGQ2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4159555344,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADVTXJZK5QRQXJA4425D2T4TMZOXAVCNFSM6AAAAACXFGE2SCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNJZGU2TKMZUGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

No I do not. On Mon, Mar 30, 2026 at 8:11 PM fcannini ***@***.***> wrote: > *fcannini* left a comment (mighty-gerbils/gerbil#1422) > <https://github.com/mighty-gerbils/gerbil/issues/1422#issuecomment-4159555344> > > @drewc <https://github.com/drewc> You have no idea how aggressive and > condescending you're coming across, do you? > > — > Reply to this email directly, view it on GitHub > <https://github.com/mighty-gerbils/gerbil/issues/1422?email_source=notifications&email_token=AADVTXJXNK36I23R2VWPCT34TMZOXA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJVHE2TKNJTGQ2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4159555344>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AADVTXJZK5QRQXJA4425D2T4TMZOXAVCNFSM6AAAAACXFGE2SCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNJZGU2TKMZUGQ> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

fcannini commented

2026-04-01 17:03:55 +00:00

(Migrated from github.com)

@vyzo Please let me know if I may be of any help.