I came up on it in the context of making build chroots. They don't need python installed even on Ubuntu, and nothing causes it to be there until you install lsb-release. And as it has to be unpacked for every build it's good to keep the size/bloat down.
I assume that python is still listed in dependencies in Ubuntu so it will be brought in for packages that need it? You are right that this is much worse problem on Debian. But for tools that need to work on Debian and Ubuntu (I came across this working on xapt) they need a way to decide which repository layout details to use. lsb-release seems a nice clean way but it's not acceptable on the Debian side if it brings in python. This is actually quite a general problem which affects various tools. A clean and low-overhead method of choosing behaviour would be good. Another approach is to move anything that changes out into config files so each distro is statically configured, but it seemed nice to make the tools just DTRT so even if run in the wrong place they would work. -- lsb_release requires >9MB of Python, replace with C/Shell script https://bugs.launchpad.net/bugs/646795 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
