Bug 2238264 - Migrate to active fork `eza`
Summary: Migrate to active fork `eza`
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: rust-exa
Version: 38
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Rust SIG
QA Contact: Fedora Extras Quality Assurance
URL: https://github.com/ogham/exa#exa-is-u...
Whiteboard:
Depends On: 2066343 2133308 2235482 2238566 2238567 2238568 2240660
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-09-11 03:44 UTC by cyq
Modified: 2023-10-01 16:25 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-10-01 16:25:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description cyq 2023-09-11 03:44:16 UTC
The original `exa` project is unmaintained and deprecated in favour of the active fork `eza`, due to the project owner having been unreachable for two years (I wish him well).

The active fork has lots of fixes and a handful of noteworthy features (particularly important to Fedora, SELinux context support with `-Z`).

See also:

https://github.com/ogham/exa#exa-is-unmaintained-use-the-fork-eza-instead
https://bugzilla.redhat.com/show_bug.cgi?id=2214215
https://gitlab.archlinux.org/archlinux/packaging/packages/eza/-/blob/main/PKGBUILD?ref_type=heads

Comment 1 Fabio Valentini 2023-09-12 13:01:04 UTC
Yup, this is on my TODO list.

Compared to the last version of exa, eza depends on a few new crates / forks that will need to be packaged:

- ansiterm ^0.12 (new)
- gethostname ^0.4 (currently at 0.2.3)
- git2 ^0.18 (currently at 0.17.2)
- proc-mounts ^0.3 (currently at 0.2.4)
- timeago ^0.4.1 (new)
- uzers ^0.11.2 (new)

Comment 2 Fabio Valentini 2023-09-12 13:22:19 UTC
New dependencies packaged and submitted for review.

Comment 3 Fabio Valentini 2023-10-01 16:25:59 UTC
Packages for eza are built for all current branches of Fedora.

They should be available from package repositories within 24 hours:
https://bodhi.fedoraproject.org/updates/?packages=rust-eza

I'm not sure whether users who have exa installed should be migrated to eza automatically, but this can be handled later.


Note You need to log in before you can comment on or make changes to this bug.