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

Opam removes files too late in the upgrade #405

Closed
chambart opened this issue Jan 21, 2013 · 4 comments
Closed

Opam removes files too late in the upgrade #405

chambart opened this issue Jan 21, 2013 · 4 comments

Comments

@chambart
Copy link
Contributor

When ocp-build 0.1 is installed, installing typerex force the upgrade of ocp-build to 1.99-beta (only a dependency to typerex), but it seems that ocp-build.0.1 is removed after installing typerex. So the bin/ocp-build binary installed by typerex is removed.

@samoht
Copy link
Member

samoht commented Jan 21, 2013

Which version of opam are you running ? A bug like this existed in 0.8.3 but it should be fixed in 0.9.1.

@chambart
Copy link
Contributor Author

opam --version
0.9.2

@samoht
Copy link
Member

samoht commented Jan 22, 2013

Hum actually I'm not sure how to fix this properly. Just to be clear, this is the current sequence of event:

  • typerex is installed: this installs the ocp-build binary
  • ocp-build.0.1 is removed: this removes the ocp-build binary
  • the new ocp-build package is installed: this is a virtual package so it doesn't do anything

I guess the right solution is to remove all the packages first, and the install then. Unfortunately, this is not a trivial change in the current way we are processing package actions.

@chambart
Copy link
Contributor Author

One other solution would be to have a cleaner ocp-build install:

  • install typerex only build files and keep them somewhere for future packages to get them
  • install ocp-build only copy the ocp-build binary from the directory where typerex was built to bin/ocp-build

Is adding something to ask the building of a package to happen inside the build directory of another reasonable ?

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

2 participants