Search Criteria
Package Details: erlfmt-git 1.6.0.r0.g94e6c0d-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/erlfmt-git.git (read-only, click to copy) |
|---|---|
| Package Base: | erlfmt-git |
| Description: | An automated code formatter for Erlang |
| Upstream URL: | https://github.com/WhatsApp/erlfmt |
| Keywords: | codeformatter erlang |
| Licenses: | Apache-2.0 |
| Provides: | erlfmt |
| Submitter: | ehedlund |
| Maintainer: | ehedlund |
| Last Packager: | ehedlund |
| Votes: | 1 |
| Popularity: | 0.55 |
| First Submitted: | 2024-12-09 21:19 (UTC) |
| Last Updated: | 2025-02-09 17:42 (UTC) |
Dependencies (3)
- erlang-core
- git (git-gitAUR, git-glAUR) (make)
- rebar3 (rebar3-gitAUR) (make)
Latest Comments
tuhtah commented on 2025-02-09 21:21 (UTC) (edited on 2025-02-09 21:26 (UTC) by tuhtah)
Likewise, thank you for the quick response and fix. Works like a charm! And yes, I used the rebar3 version from the official repos for my tests.
ehedlund commented on 2025-02-09 17:43 (UTC)
Nvm, they have apparently added rebar3 to the official repos. The depends should be updated now. Thank you for your help and feedback!
ehedlund commented on 2025-02-09 17:34 (UTC)
Hi, I see that the package should be updated to depend on erlang-core instead. However, rebar3-git depends on the erlang-nox package which creates a conflict when I try to move to erlang-core.
Do you have a separate rebar3 install? Or am I missing something?
tuhtah commented on 2025-02-09 15:12 (UTC) (edited on 2025-02-09 15:12 (UTC) by tuhtah)
Recently Arch Linux switched from erlang-nox to an erlang split package approach.
See: https://archlinux.org/todo/migrate-from-erlang-nox-to-erlang-split-package/ https://archlinux.org/packages/extra/x86_64/erlang-core/
Updating the depends= line from erlang-nox to erlang-core seemed to be enough on my amd64 system. (tested with an archlinux docker container)
Thank you for your maintenance of the tool.
micwoj92 commented on 2025-01-14 21:47 (UTC)
Thanks
ehedlund commented on 2025-01-14 21:38 (UTC)
Okay, the
pkgver()should use tags now if I have understood correctly. Thank you for your help and feedback!micwoj92 commented on 2025-01-14 20:04 (UTC)
https://wiki.archlinux.org/title/VCS_package_guidelines#Git
It is preferred, in this page you can read "If there are no tags then use number of revisions since beginning of the history: ", but in this repo there are tags so they should be used.
ehedlund commented on 2025-01-14 01:15 (UTC)
@micwoj92 I'm not quite sure what you mean. Do you mean
git tag? If so, could you please tell me why that is more desirable than the current version tag?micwoj92 commented on 2025-01-13 22:43 (UTC)
Please use tags for pkgver