-
-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Samba: reduce bloat by linking dynamically #110
Comments
Add Transmission BitTorrent service
@edolstra Have you had a chance to look into this yet? Do you plan to get it in before |
@wkennington: any ideas about this issue? I see the size of |
Yeah, exactly. Light is just nicer in the sense that you have far fewer
|
|
Hotfix, solving issues with lz4cat. - Fixed: incompatibility sparse mode vs console (#105) - Fixed: LZ4IO exits too early when frame crc not present (#106) - Fixed: incompatibility sparse mode vs append mode (#110) - Performance fix: big compression speed boost for clang (+30%) - New: cross-version test
Samba is now 52MiB and the entire closure is 225MiB, of which 90MiB come from Python and Perl. Should this issue be closed? |
I do think so. Also |
It might still be possible to improve. I suspect many reverse dependencies use mainly the libraries, so the ~13 MB in |
dell/xps/13-9380: also import intel profile
Samba is insanely bloated:
The main reason seems to be that the binaries in bin and sbin are statically linked against libsmbclient and libnetapi, even though we build dynamic versions of those.
The Samba source code says:
so it's not clear if dynamic linking is currently safe. However, https://bugs.archlinux.org/task/24678 suggests that using Samba's alternative "waf"-based build system does the right thing. So maybe we should investigate that.
The text was updated successfully, but these errors were encountered: