Summary: | databases/mysql80-server excessive free storage requirements for building from source | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Viktor Štujber <viktor.stujber+freebsd-bugs_v4CCPfay> |
Component: | Individual Port(s) | Assignee: | Jochen Neumeister <joneum> |
Status: | Closed FIXED | ||
Severity: | Affects Only Me | CC: | joneum |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(joneum) |
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
Viktor Štujber
2021-02-28 11:18:46 UTC
Does the problem still exist? I do not see any related changes in the port makefile, and the issue was not yet raised upstream, so I assume things remain the same. Regarding the huge distfile, 85% of it is testing files. Removing tests and repacking with lzma2 can reduce it from 278MB to 27MB. But that's an extreme change. Regarding the unpacked source tree, deleting mysql-test/ when tests are disabled would save 516MB. There is currently no port option to disable tests. Another bugreport suggested CMAKE_ARGS += -DWITH_UNIT_TESTS=OFF, I don't know if it actually works. I am currently using a local port modification that deletes the test directory in post-extract. Regarding the build forcing retention of intermediate object files even though the targets are already built, and not cleaning them up gradually as they are built, is a structural build system inefficiency that would have to be addressed upstream. Regarding the staging directory holding copies instead of symlinks/hardlinks, it's just a simple idea that I had when going over the build output. I don't know how the build system picks which files to stage, or how it stages them, but I assume it's done via simple file copy. This is something that Mk\bsd.port.mk would be handling. The motivation behind this was that in the past, it used to be possible to build mysql-server on tmpfs comfortably on a cheap pc, without consuming all available system memory and/or running out and not being able to complete the build. Since no one else has posted on this problem, or had the same problem, I'm closing here. If you have further problems with this topic feel free to open it again |