FS#79613 - [exa] now deprecated, switch to community maintained replacement

Attached to Project: Arch Linux
Opened by George Rawlinson (rawlinsong) - Thursday, 07 September 2023, 20:48 GMT
Last edited by Toolybird (Toolybird) - Saturday, 09 September 2023, 02:07 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Alexander F. Rødseth (xyproto)
Caleb Maclennan (alerque)
kpcyrd (kpcyrd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: the maintainer of exa has essentially abandoned it, there is a replacement known as eza.

See upstream repository’s README: https://github.com/ogham/exa
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 09 September 2023, 02:07 GMT
Reason for closing:  Fixed
Additional comments about closing:  eza 0.11.0-2
Comment by Mark Wagie (yochananmarqos) - Thursday, 07 September 2023, 20:57 GMT Comment by George Rawlinson (rawlinsong) - Thursday, 07 September 2023, 21:41 GMT
Ah okay, in that case, it would be better to remove exa from the repositories and have eza provide exa.
Comment by kpcyrd (kpcyrd) - Friday, 08 September 2023, 00:34 GMT
I'm fine with having exa removed eventually, I'm wondering if the eza package should provide a compatibility symlink for the `exa` binary name to avoid breaking user's systems (I'm also fine with additional maintainers joining eza).

Also at which point should users be migrated, the fork currently has ~600 github stars (is this sufficient signal already?).
Comment by George Rawlinson (rawlinsong) - Friday, 08 September 2023, 01:21 GMT
Considering the last change to exa’s upstream was a note explaining that the project is unable to be archived due to insufficient access, I would say that now is a good time to migrate.

I’m not a maintainer for either package, but the suggested changes (symlinking eza/exa & having eza provide/replace exa) sound amenable enough to me as a user.

Loading...