Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

app-forensics/libewf removal in Gentoo #274

Closed
a17r opened this issue Mar 17, 2018 · 2 comments
Closed

app-forensics/libewf removal in Gentoo #274

a17r opened this issue Mar 17, 2018 · 2 comments

Comments

@a17r
Copy link

a17r commented Mar 17, 2018

This package is currently pending removal in Gentoo because no one volunteered to (proxy-)maintain it. It only caught my attention because I was looking at a testdisk-7.1 version bump (for dropping the Qt4 revdep).

https://bugs.gentoo.org/547418

@blshkv: At a first glance your ebuild in pentoo-overlay looks technically sound. I thought it would make sense to drop you a note on this since you are already doing the work in pentoo-overlay on GitHub, you may as well consider submitting your libewf ebuilds to Gentoo, which under gentoo-proxy-maint imo is a straightforward way to directly contribute via PRs.

@blshkv
Copy link
Contributor

blshkv commented Mar 17, 2018

I would be happy if Gentoo could take it over, but I don't see the point in proxy maintenaning. It's basically a double work for me. Use pentoo overlay if you need out tools :)

@blshkv
Copy link
Contributor

blshkv commented Mar 18, 2018

Hi again, I looked at the issue in the morning and here is the conclusion.

The current libewf situation is a mess. This library does NOT provide a stable API and not ready for production (forensic especially) use in general. Every new "experimental" or "alpha" version of libewf might change an API and forensic tools must review and test it. See guymanager, for example:
https://sourceforge.net/p/guymager/feature-requests/11/ . Its author decided to fork libewf so he can rely on it.

So a libewf maintainer must make sure that all tools are compatible (or compile at least) with the current version and monitor upstreams or/and apply upstream/random patches. However, this mess should not be kept in the main tree and deserve removal.

I will try to maintain it in Pentoo but use it at your own risk.

@blshkv blshkv closed this as completed Mar 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants