From a4b51a8dfe9d8176004e1fb081cefcc8d8f8f029 Mon Sep 17 00:00:00 2001 From: Didier Raboud Date: Fri, 22 Feb 2019 10:50:50 +0100 Subject: [PATCH] 914897: Add a rebuttal point --- 914897_merged_usr/ballot.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/914897_merged_usr/ballot.md b/914897_merged_usr/ballot.md index 970dac0..4262f50 100644 --- a/914897_merged_usr/ballot.md +++ b/914897_merged_usr/ballot.md @@ -14,7 +14,8 @@ The motivation to get Debian systems to converge towards such a scheme is vastly The arguments against moving the base directories' scheme towards "merged `/usr`" are as follows: * there's no gain in disrupting something that is not inherently broken; -* `/{bin,sbin,lib*}/` → `/usr/{bin,sbin,lib*}/` symlinks create confusing views of the system (`/bin/cat` and `/usr/bin/cat` are the same file), and dpkg doesn't support this situation cleanly [#134758](https://bugs.debian.org/134758). +* `/{bin,sbin,lib*}/` → `/usr/{bin,sbin,lib*}/` symlinks create confusing views of the system (`/bin/cat` and `/usr/bin/cat` are the same file), and dpkg doesn't support this situation cleanly: [#134758](https://bugs.debian.org/134758). +* it is possible for distributions to converge towards having all system files in `/usr` in finite time instead of shortcutting this migration with `/{bin,sbin,lib*}/` → `/usr/{bin,sbin,lib*}/` symlinks. [0]: https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/ [1]: https://wiki.debian.org/UsrMerge -- 2.39.2