Re: [Chicken-janitors] #1218: chicken-install may fail if TMPDIR is mounted noexec (depending on setup-file details)

[Ivan Raikov]

It considerably limits the effectiveness of distributing software
written in Chicken, because now users who are not familiar with its
peculiarities cannot simply run chicken-install. Could at least some
option be added so that the user home directory is used instead of
TMPDIR?

On Sat, Apr 22, 2017 at 6:37 AM, Chicken Trac <address@hidden> wrote:
> #1218: chicken-install may fail if TMPDIR is mounted noexec (depending on 
> setup-
> file details)
> -----------------------------------+--------------------
>             Reporter:  iraikov     |      Owner:
>                 Type:  defect      |     Status:  new
>             Priority:  major       |  Milestone:  5.0
>            Component:  extensions  |    Version:  4.10.x
>           Resolution:              |   Keywords:  coops
> Estimated difficulty:  hard        |
> -----------------------------------+--------------------
>
> Comment (by sjamaan):
>
>  The new setup language cleanly separates build from install, which means
>  the problem still exists.
>
>  I think the clean separation is desirable because you want to be able to
>  build separately, and also because if the building of coops works and is
>  installed, but coops-primitive-objects fails, this means the egg would be
>  half-installed.
>
>  I don't know if it's even something we ''can'' fix (or even should fix?).
>  Perhaps it should be documented as a limitation. I think even detecting
>  this situation is difficult.
>
> --
> Ticket URL: <https://bugs.call-cc.org/ticket/1218#comment:10>
> CHICKEN Scheme <https://www.call-cc.org/>
> CHICKEN Scheme is a compiler for the Scheme programming language.