Arch Linux User Repository

@tleican I'm planning to move this package to [extra], and adopt+maintain it there, if you don't mind.

Ive been having an issue building version 1.9.1-1

error: failed to load manifest for workspace member `~/.cache/paru/clone/gleam/src/gleam-1.9.1/gleam-bin`
referenced by workspace at `~/.cache/paru/clone/gleam/src/gleam-1.9.1/Cargo.toml`

Caused by:
  failed to parse manifest at `~/.cache/paru/clone/gleam/src/gleam-1.9.1/gleam-bin/Cargo.toml`

Caused by:
  feature `edition2024` is required

  The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this version of Cargo (1.85.0-nightly (66221abde 2024-11-19)).
  Consider adding `cargo-features = ["edition2024"]` to the top of Cargo.toml (above the [package] table) to tell Cargo you are opting in to use this unstable feature.
  See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#edition-2024 for more information about the status of this feature.
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'gleam-1.9.1-1':
error: packages failed to build: gleam-1.9.1-1

It got resolved by running rustup update. i didn't think it was using my local rust version or whatever.

Worm regards, John

@rehhouari @mia Thanks for the heads-up.

It's better for the 2 gleam packages to be similar-ish, so I've followed your approach for direct, and optional dependencies. Maybe depending on full blown erlang would be safer, but there is time to adjust with follow-up releases of Gleam.

Following the switch from erlang-nox to erlang-core, the erlang-eunit package stopped being installed with the gleam package. Gleam's default template includes a dependency on gleeunit, which depends on erlang-eunit, so the default package template is currently not building on new installs. For now, it would be good to add erlang-eunit as a dependency of gleam (I just added it as a dependency of gleam-bin). A more long-term solution might be making a new headless virtual package that depends on all of the components of erlang that don't depend on erlang-wx, but if @xyproto is moving gleam to [extra] that may be wasted effort.

As of the latest version, currently 1.8.1, new gleam projects no longer run without the erlang-eunit package.

However it would be optimal to add the entire erlang package as a dependency to avoid future dependency problems such as this one.

As per the Gleam creator @lpil's comment on this issue in the Gleam discord: "In the Erlang world it is expected that you have the standard Erlang distribution".

Thanks for the heads-up @gdamjan.

I've switched to erlang-core for now, and added rebar3 as an optional dependency (which may be needed to build packages from hex.pm later).

this needs to depend on erlang-core now, or maybe even erlang-compiler ?

now == since https://gitlab.archlinux.org/archlinux/packaging/packages/erlang/-/commit/f5885e09a7899a2b2a5f894bdd9dbd363cc9ebe1

also, it should probably have an optdepend on rebar3

Just a hint: Rust needs to be updated to 1.82 or the compilation will fail:

   Compiling gleam-wasm v1.6.1 ()
error[E0432]: unresolved import `std::panic::PanicHookInfo`
 --> compiler-cli/src/panic.rs:2:5
  |
2 | use std::panic::PanicHookInfo;
  |     ^^^^^^^^^^^^-------------
  |     |           |
  |     |           help: a similar name exists in the module: `PanicInfo`
  |     no `PanicHookInfo` in `panic`

For more information about this error, try `rustc --explain E0432`.
error: could not compile `gleam` (bin "gleam") due to 1 previous error

So check your Rust version ($ rustc --version) before installing this package, or run command $ rustup update stable to update.

Looking forward to seeing this land in [extra]!

@xyproto Is that a real question or a "I'm taking over" notice? :)

(Edit: I mean, it's good to see gleam graduate to an official package, so do proceed!)

@tleican I'm planning to move this package to [extra], and adopt+maintain it there, if you don't mind.