[arch-general] ettercap new upstream
Hi, some month ago I decided to become the new ettercap upstream maintainer. I released a fixed 0.7.4 version - https://github.com/drizztbsd/ettercap/tarball/NG-0.7.4 - that is included in debian testing and sid. Should I flag the ettercap package as old? -- Timothy M. Redaelli IT Consultant Email: timothy@redaelli.eu Mobile: +39 (338) 1187273 Skype: redatim
30.08.2011 21:04, Timothy M. Redaelli kirjoitti:
Hi, some month ago I decided to become the new ettercap upstream maintainer. I released a fixed 0.7.4 version - https://github.com/drizztbsd/ettercap/tarball/NG-0.7.4 - that is included in debian testing and sid.
Should I flag the ettercap package as old?
Ofcourse ^^ you should, it is now out-of-date after all.
Hi Tim, Does your version complain about GCC and other jibber jabber? I need to know if your fork compiles fine under Arch, especially the GTK frontend. -- Bl@ster / dottorblaster
On 30 August 2011 20:37, Alessio 'Blaster' Biancalana
Hi Tim, Does your version complain about GCC and other jibber jabber? I need to know if your fork compiles fine under Arch, especially the GTK frontend.
You can compile my (git) version from aur (package ettercap-drizzbsd). I tested it compiled with gcc 4.6.1 and clang (git version). gcc still emits some warnings, especially under amd64 platform (for the different size of pointers), but ettercap (also the GTK gui) works without any problem.
Did you think to provide a stable tarball? I don't think git clone is a good idea for an extra and stable package ;) -- Bl@ster / dottorblaster
participants (3)
-
Alessio 'Blaster' Biancalana
-
Jesse Jaara
-
Timothy M. Redaelli