Publishing eww on crates.io #1390
Description
Hey, I've been writing effectively my own "magic variables" supplied by a different service, and passing them to eww via eww update.
Given that eww update really just opens a unix socket to send a message, and I'm writing my service in Rust, calling out to the eww binary feels inefficient. I was thinking of short-circuiting this by opening the socket in my service directly and just sending across the message. eww exposes all of the relevant structs as pub.
But it doesn't seem like eww is actually published on crates.io, making this somewhat annoying because I need to use a git dependency. As of #1076 publishing eww as a crate should be trivial (and get rid of the defunct crate that's parked there currently) - is there a particular reason this isn't done yet?