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

Release required to be compatible with mir-algorithm > 0.9.0 #29

Open
drug007 opened this issue Jun 8, 2018 · 4 comments
Open

Release required to be compatible with mir-algorithm > 0.9.0 #29

drug007 opened this issue Jun 8, 2018 · 4 comments

Comments

@drug007
Copy link

drug007 commented Jun 8, 2018

mir-glas has depedency on mir-algorithm:
"mir-algorithm" : ">=0.6.9 <0.9.0"
that prevents using newer version of mir-algorithm

@wilzbach
Copy link
Member

wilzbach commented Jun 8, 2018

Maybe it's time to go back to a single repo and use dub sub packages?
This would still allow users to just use the sub modules they are interested in, but avoid all these versions problems.
Also it would make docs and tooling easier.

@drug007
Copy link
Author

drug007 commented Jun 8, 2018

Probably, but I wasn't satisfied using subpackages in my own projects too. Certainly it should be discussed - what are the reasons that separate repos used instead of subpackages.

@wilzbach
Copy link
Member

wilzbach commented Jun 8, 2018

Would you mind explaining why you didn't like them in your personal projects?

@drug007
Copy link
Author

drug007 commented Jun 8, 2018

Frankly speaking I can't remember, this decision was made long time ago. Probably because subpackages aren't convenient during developing. But definitely separate repos aren't good enough too. I now use single repo with separate packages that can depends on other packages using:
dependency other_package path="../other_package" version="*".
At least this way let me avoid version mismatching.

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