You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My bindgen wrappers support niceties like log redirection through the log crate and static linking, but my svt-av1-sys is probably otherwise functionally identical to this one. However, I'd like to publish all three crates (svt, svt-av1-sys, and svt-hevc-sys) together, since the first depends on the other two. I can't do that because svt-av1-sys is taken on crates.io.
Given that this seems mostly unmaintained anyway, I was wondering if you would mind me taking over the crate name and publishing my version instead? If you don't want to, I understand, and there are workarounds I could employ (for example, calling mine svt-av1-sys-next or something gross like that).
Thanks in advance for your thoughts!
The text was updated successfully, but these errors were encountered:
Hi folks,
I recently wrote bindgen wrappers for svt-av1 and svt-hevc, as well as higher level rust bindings: https://github.com/colinmarc/svt-rs/
My bindgen wrappers support niceties like log redirection through the
log
crate and static linking, but my svt-av1-sys is probably otherwise functionally identical to this one. However, I'd like to publish all three crates (svt
,svt-av1-sys
, andsvt-hevc-sys
) together, since the first depends on the other two. I can't do that becausesvt-av1-sys
is taken on crates.io.Given that this seems mostly unmaintained anyway, I was wondering if you would mind me taking over the crate name and publishing my version instead? If you don't want to, I understand, and there are workarounds I could employ (for example, calling mine
svt-av1-sys-next
or something gross like that).Thanks in advance for your thoughts!
The text was updated successfully, but these errors were encountered: