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

rename mirage-conduit into conduit-mirage #231

Closed
samoht opened this issue Jul 25, 2017 · 5 comments
Closed

rename mirage-conduit into conduit-mirage #231

samoht opened this issue Jul 25, 2017 · 5 comments

Comments

@samoht
Copy link
Member

samoht commented Jul 25, 2017

Not sure why this is in reverse vs. all other conduit-* package names.

@avsm
Copy link
Member

avsm commented Jul 25, 2017

because this is what it was before -- I wanted to leave the package names as similar as possible and then make all the changes in one go across various projects (e.g. mirage-http, mirage-conduit, mirage-dns) and to clearly deprecate the old packages to avoid confusion. I'm still confused by tar-format->tar and git-mirage, since the older packages are still around.

@samoht
Copy link
Member Author

samoht commented Jul 25, 2017

I think removing the names which doesn't follow the conventions should remove the confusion :-)

But yes, I guess it's ok to do that progressively!

@avsm
Copy link
Member

avsm commented Jul 25, 2017

but we can just delete the old packages -- they are still in opam-repository and show up in searches. So we do need some mechanism (e.g. messages) of deprecating them and/or edit the short descriptions to reflect that they were part of MirageOS2 or something...

@avsm
Copy link
Member

avsm commented Jul 25, 2017

for example try opam list --depends-on mirage-unix and try to figure out which of those packages are still relevant :)

@samoht
Copy link
Member Author

samoht commented Sep 5, 2017

Duplicate of #178

@samoht samoht marked this as a duplicate of #178 Sep 5, 2017
@samoht samoht closed this as completed Sep 5, 2017
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