On 05/11/2024 21:39, Fabio Valentini
wrote:
Difficult to say right now, but I believe enough.On Tue, Nov 5, 2024 at 9:33 PM Arthur Bols <arthur@xxxxxxxx> wrote:Hi Fabio, On 31/10/2024 19:38, Fabio Valentini wrote: Hi all, TL;DR: I am planning to orphan rust-eza later today. Be warned - it's a lot of work to keep up with upstream (~1 release per week), keeping it up-to-date in epel8 is a bit painful (because RHEL 8, duh), and there are license shenanigans afoot since the v0.20.0 release (package is currently at v0.19.3). Given that I don't even use eza myself and just packaged it because it was on some people's wishlist as the maintained fork of exa, I really cannot justify the ongoing cost of maintaining this package to myself. I'm interested in maintaining eza since I use it on multiple systems. I'm a bit hesitant, though. First, I won't have time to keep up with every upstream release, but I'll do my best to keep it updated. Also, because of the large dependency tree, I think joining the rust-sig would be helpful so I can update dependencies as needed (and of course, I'll try to help others out where I can). Finally, my experience with Rust is limited, but I am quite familiar with the packaging process.Well .. I guess it depends on how much time you can invest into this? And if you want to deal with the licensing mess mentioned below? :)
I can understand that. Unfortunately it is a great tool... :/ I'm going to sleep on it.It might be of note that the project was relicenced from MIT to EUPL-1.2 without much fanfare as of the 0.20.0 release, in this mess-of-a-PR: https://github.com/eza-community/eza/pull/1155 - I'm not a lawyer, but the maintainer unilaterally slapping a different license onto a project that's been around since 2017 in some form without asking other contributors (or the original author of exa) doesn't pass the smell test for me. Seriously... https://github.com/eza-community/eza/releases/tag/v0.20.0 The PR mentions dual-licensing, but it's now a mess of only MIT, MIT or EUPL-1.2, and only EUPL-1.2...Yes. I wasn't joking when I said it was a mess-of-a-PR :) That mess alone would make me hesitant to want to continue maintaining (or using) this project. :(
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
