I guess there's another project for me, once I finish writing a somewhat complex, networked application in Scheme, and building a Bryan Cantrill Bingo Sheet generator (which would be trivial, if I could ever get around to it).
Hey, no matter how silly the idea, I have to keep in practice somehow.
Great idea, but the delivery leaves much to be desired: I am not going to run "pip install" and bypass the software management subsystem of my operating system, thereby compromising the integrity of my system. No OS package, no install.
He already provides packaging for Arch, probably what he uses. It's probably just a question of what resources he has available. Many of us are content to use a tarball or pip.
The distribution packages are often carefully tuned to match compatible versions, with pip, you might add something that the packaging system doesn't account for. I disliked pip ever since but the virtualenv idea sounds good.
My operating system wouldn't know about this new content, which means that it would not be automatically reproducible. There would now be a change to the system that the system doesn't know about.
I don't do that. On my system every single change to every single file is encapsulated inside of an OS package. The integrity of the OS content is not compromised in any way, because the OS knows about every single application's file. Emphasis on application's file, as opposed to just raw data.
