install: first install code, then binaries

Since installing code will also delete a directory tree, it should run
first. This avoids exotic cases where it deletes the binaries it just
installed.

Use case: co-installing python2/python3 using a bindir bundled with the
rest of calibre's code, in order to maintain an alternatives system
pointing symlinks in /usr/bin at the configured binaries.
This commit is contained in:
Eli Schwartz 2019-05-12 01:48:20 -04:00
parent 121a5acad0
commit ae02c30a17
No known key found for this signature in database
GPG Key ID: CEB167EFB5722BD6

View File

@ -135,8 +135,8 @@ class Develop(Command):
self.opts = opts self.opts = opts
self.regain_privileges() self.regain_privileges()
self.consolidate_paths() self.consolidate_paths()
self.write_templates()
self.install_files() self.install_files()
self.write_templates()
self.run_postinstall() self.run_postinstall()
self.install_env_module() self.install_env_module()
self.success() self.success()