Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[suggestion] Separate binary dependencies #11

Open
makapuf opened this issue Nov 22, 2023 · 2 comments
Open

[suggestion] Separate binary dependencies #11

makapuf opened this issue Nov 22, 2023 · 2 comments

Comments

@makapuf
Copy link

makapuf commented Nov 22, 2023

There are several ways to to simplify build and not require many dependencies not needed for library usage, see by example:

https://stackoverflow.com/questions/35711044/how-can-i-specify-binary-only-dependencies

@makapuf makapuf changed the title Separate binary dependencies [suggestion] Separate binary dependencies Nov 22, 2023
@therealprof
Copy link
Member

While that is true, you might have noticed that the few dependencies we have (serde, quick-protobuf, clap and anyhow) are used even in the library part. It might be possible to make that leaner but that doesn't seem to warrant the effort. At least our library users also have the same dependencies themselves.

@makapuf
Copy link
Author

makapuf commented Nov 22, 2023

You're right of course : I wasn't using those parts, focusing on serializing / deserializing USP without encoding it to json or using the commandline. Ideal would be a feature toggle, but I maybe that would be more complex than useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants