On 2019-05-22 11:39, Jonas Smedegaard wrote: > You can save some by avoiding network-manager.
Probably a good idea, but not so good for that specific system. It uses a lot of NM (and MM) functionality. Too bad, that they more than tripled in size. I'll check, whether I can build NM and MM with some options to decrease size and dependency tree. Btw, MM is not as convenient to compile as before. In squeeze, MM was cross-buildable easily. Now it makes use of GIR stuff, which breaks cross-compilation. (One can remove it from the Debian build, so MM is still cross-buildable, but not as easy as before.) Note to myself: Avoid everything that uses GIR. > Check if you use _both_ python2 and python3, and consider avoiding the > parts pulling in one of them. No, we moved from Python 2 to Python 3, see my table. The Python 3 binary alone is *much* larger than the Python 2 binary. > I'd be happy to try analyze more closely, and perhaps codify as a boxer > profile, if your system setup is not a secret. Unfortunately, some parts of it are completely non-free :-( But I'm allowed to talk about it, there's no gag order.
