Add libkrw and libkrw-dopamine

[Cryptiiiic]

All Submissions

• [x] Have you made sure there aren't any other open Pull Requests for the same update/change?
• [ ] This Pull Request doesn't contain any package additions; it's a small change (e.g README change)

Package Additions/Updates

• [x] Have you confirmed this builds & works as intended on an iOS device (if applicable)?
• [ ] Have you confirmed this builds & works as intended on a macOS device (if applicable)?

[ghost]

I'd add a Provides: libkrw (= @DEB_LIBKRW_V@) to libkrw0 so other packages that depend on just libkrw can find it.

[Cryptiiiic]

I'd add a Provides: libkrw (= @DEB_LIBKRW_V@) to libkrw0 so other packages that depend on just libkrw can find it.

They said don't do this

[ghost]

Why the hell would you not do that? You're forcing every tweak that previously depended on libkrw to be explicitly updated to also allow for libkrw0 when it's the same thing under the different name.

[Cryptiiiic]

Why the hell would you not do that? You're forcing every tweak that previously depended on libkrw to be explicitly updated to also allow for libkrw0 when it's the same thing under the different name.

@0xallie libkrw.dylib isn't the same thing as libkrw.0.dylib, thats the reasoning, I doubt you will change their mind

[ghost]

That's great, now every tweak will have to do Depends: libkrw | libkrw0 | libkernrw. As if two competing implementations wasn't enough, now there's three. Way to create unnecessary confusion and burden on developers. The whole point of libkrw was to be a unified extensible interface.