I've been working on developing a library that builds upon libafl_nyx. I've noticed that it isn't published on crates.io at all; this makes it difficult to work with when I'm pulling other libraries in that build upon libafl but reference the crates.io version, not the git version. The current fix (changing dependencies all to git) would constitute traversing dependencies I'm pulling in and patching their sources, which isn't the most ideal solution.
Can libafl_nyx be published on crates.io, or are there technical hurdles preventing such? I realize it has a lot of moving parts in its build system and packer to make everything work right; I just wanted to make sure there wasn't an easy publish that could happen before I go ahead with switching all my dependencies to the libAFL git repo.
I've been working on developing a library that builds upon
libafl_nyx. I've noticed that it isn't published on crates.io at all; this makes it difficult to work with when I'm pulling other libraries in that build uponlibaflbut reference the crates.io version, not the git version. The current fix (changing dependencies all to git) would constitute traversing dependencies I'm pulling in and patching their sources, which isn't the most ideal solution.Can
libafl_nyxbe published on crates.io, or are there technical hurdles preventing such? I realize it has a lot of moving parts in its build system and packer to make everything work right; I just wanted to make sure there wasn't an easy publish that could happen before I go ahead with switching all my dependencies to the libAFL git repo.