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

property for conflicts #117

Open
yrashk opened this issue Feb 19, 2011 · 2 comments
Open

property for conflicts #117

yrashk opened this issue Feb 19, 2011 · 2 comments

Comments

@yrashk
Copy link
Member

yrashk commented Feb 19, 2011

to avoid situations like mochijson2 + mochiweb

@yrashk
Copy link
Member Author

yrashk commented Feb 19, 2011

(00:31) < etrepum> yeah but that's shitty because people will have both
(00:31) < etrepum> e.g. I depend on a library that only uses mochijson2 so it's a transitive dependency, but I also use mochiweb

@yrashk
Copy link
Member Author

yrashk commented Feb 19, 2011

conflict property might also have an option for describing supersets.

like {conflicts, ["somelib", {overrides, "another"}]}

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

No branches or pull requests

1 participant