downhill You seem to be under the impression that replacing eopkg means changing the .eopkg file format. That's actually the opposite of our initial goal, which is full compatibility with the existing file format. I'll admit that I would eventually like to change the format, but when we do so, you as an end-user would never notice.
The primary goal and necessity of replacing eopkg is to move from a python2 application which is easily broken and holding up deprecation of python2, to a statically-compiled binary which can easily be repaired and cannot be broken by something as trivial-sounding as a pip install.
