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

inotify transitive dependency #176

Closed
russel opened this issue Feb 5, 2019 · 2 comments
Closed

inotify transitive dependency #176

russel opened this issue Feb 5, 2019 · 2 comments

Comments

@russel
Copy link

russel commented Feb 5, 2019

When I use notify, I get inotify as a transitive dependency. Seems entirely reasonable. However, inotify has optional dependencies. It seems these are always pulled in when depending on notify. Is there any way of pulling in notify but not pulling in the optional dependencies of inotify?

@passcod
Copy link
Member

passcod commented Feb 5, 2019

To be clear: Cargo doesn't do "optional dependencies". Deps are marked optional when they're required by features instead of the core code. In inotify's case, the stream feature has a bunch of extra dependencies, and that feature is marked as default, so its deps are pulled in.

In our case, we don't actually use inotify's stream feature, so I'll go turn that off. Just providing some background because "optional dependencies" may not have the same meaning here as you were thinking of.

@passcod passcod closed this as completed in e729e27 Feb 5, 2019
@russel
Copy link
Author

russel commented Feb 7, 2019

Indeed, my sloppy use of language around "optional", apologies for that. Thank you for making the change and publishing; I now have 31 fewer crates and no loss of functionality!

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