Compilation breaks when renaming project directory · gleam-lang/gleam#5430

(3 留言) (0 反應) (0 負責人)Rust (21,417 star) (960 fork)batch import

help wanted

描述

Renaming a gleam project directory causes a compilation error. Running the following shell commands (on Arch Linux):

gleam new repro
cd repro
gleam add lustre
gleam build
cd ..
mv repro repro_broken
cd repro_broken
gleam build

Result in the following error:

error: File IO failure

An error occurred while trying to link this file:

    /tmp/tmp.QzSnQdYrRy/repro_broken/build/dev/erlang/lustre/priv

The error message from the file IO library was:

    File exists (os error 17)

Running gleam build a second time seems to fix the error.

I routinely run into this because I run gleam projects via bind mounts in various development containers. It's a bit of a weird setup :D

I didn't do a super deep investigation but it seems related to the symlinks to priv, e.g. in build/dev/erlang/lustre:

ll build/dev/erlang/lustre
Permissions Size User   Group  Date Modified Name
...
lrwxrwxrwx     - rafael rafael  5 Mär 11:50  priv -> /tmp/tmp.QzSnQdYrRy/repro/build/packages/lustre/priv

Would it be an option to use relative links instead? Or to find broken symlinks and recreate them?

In both cases, this seems like an easy issue to fix, if someone is interested in giving some hints I'd like to make a PR :)

貢獻者指南

技術棧: rust
領域: build systemdeveloper experience
議題類型: bug
難度: 3
預計時間: 1-3 hours
活動狀態: fresh
清晰度: clear
前置要求: Understanding of symlinksGleam build processRust
新手友善度: 65
研究方向: Investigate the build system code that creates symlinks for priv directories, likely in the Erlang compilation phase. Check how the symlink path is constructed and consider using relative paths or recreating broken symlinks. The file priv symlink in build/dev/erlang/* should point to a relative path instead of absolute. Look at the build process for packages like lustre.