From ae02c30a172f9a908808b24f22c9d5b28b63da9a Mon Sep 17 00:00:00 2001 From: Eli Schwartz Date: Sun, 12 May 2019 01:48:20 -0400 Subject: [PATCH] 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. --- setup/install.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/setup/install.py b/setup/install.py index 1a99507fe2..d9380d761c 100644 --- a/setup/install.py +++ b/setup/install.py @@ -135,8 +135,8 @@ class Develop(Command): self.opts = opts self.regain_privileges() self.consolidate_paths() - self.write_templates() self.install_files() + self.write_templates() self.run_postinstall() self.install_env_module() self.success()