OK, guys, there's a misunderstand.
I'm writing an ebuild for Counter Strike.
Someone else is writing a WISE unpacker.
End-user expectations from an ebuild is that it installs requested software or assets. This is currently implemented. It will be followed up with ebuilds for FTEQW (engine) and FreeCS (libre data and game logic) in order to deliver an easy to use Counter-Strike experience for Gentoo users.
End-user expectations from any unpacker or de-archiving software, is that it reproduces the archive's content outside of the archive file. While WiseUnpacker clearly delivers much better performance, it's not perfect.
What e_wise can do better:
- work on Linux (must have) and current-day Windows (nice to have)
- preserve directory structure rather than rely on spawning Batch scripts that fill in for this shortcoming (must have)
What WiseUnpacker can do better:
- preserve directory structure (must have)
I expect to be working on more ebuilds of past proprietary games, which is why I will be using either WISE unpacking tool. Also users who install my ebuilds will probably be glad they build faster.
Abit VP6 w/ YT BIOS, 2x Tualatin-S with Connectland northbridge heatsinks, 4x512MB SDRAM PC133 CL2, SanDisk 32GB CF 160/120MB/s R/W, Plextor PX-800A, Voodoo 5500 AGP with passive mod, Voodoo 1, Yamaha YMF724F, D-Link DGE 528T rev B