--- Comment #8 from Robert-André Mauchin <> ---
> bettercap-ng *will* be merged into the bettercap original repository, commits 
> history preserved and this repo deleted, these are the steps to take in order 
> to release it as version 2.0.0 of bettercap.

Emphasis on will. Thit isn't yet bettercap 2.0, it will be in the future. I
also question the pertinence of packaging it right now instead of waiting for
the merge with bettercap. When the merge happens, we will have two packages
bettercap and bettercap-ng for the same thing, and we will have to provide an
upgrade path for one to the other. It really depends if you need this now, it
seems to still be in an alpha state.

You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
package-review mailing list --
To unsubscribe send an email to

Reply via email to