Re: Specifying private repository path for compiled executables

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

Uh, that was not ideal choice of words. I don't dislike static
linking, in fact I
prefer it for simplicity, stability and general ease of use.

The full story is, I want to package my software, some distros (e.g. Gentoo)
discourage the use of static linking for security reasons, and while it's not
forbidden to do so, I'd like to follow the guidelines as closely as possible.

On Wed, Dec 3, 2025 at 11:51 PM Pietro Cerutti <[email protected]> wrote:
>
>
> 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.
>