Re: Specifying private repository path for compiled executables

> On 2 Dec 2025, at 18:02, Alexey Egorov via Chicken-users <[email protected]> wrote:
> 
> Hello Chicken users!
> 
> I have a program suite written in Chicken, which uses a number of
> eggs, and I want to be able to distribute it without relying on user
> to install all eggs by hand.

...

> I understand that my options in this case is either link the binary
> statically, or provide -private-repository flag and put all the eggs'
> dynamic libs beside my binaries. The first solution I just don't like
> very much.

What is it that you don't like in the static linking solution?

-- 
Pietro Cerutti
I've pledged to give 10% of income to effective charities and invite you to join me.
https://givingwhatwecan.org

Sent from a small device - please excuse brevity and typos.