tmpfs
: introduce USE_TMPFS=no
to disable tmpfs usage for WORKDIR and package-specific working dirs; actually use $temp_dir_id
for mktemp; see #5502
#5506
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
tmpfs
: introduceUSE_TMPFS=no
to disable tmpfs usage for WORKDIR and package-specific working dirs; actually use$temp_dir_id
for mktemp; see #5502tmpfs
: introduceUSE_TMPFS=no
to disable tmpfs usage for WORKDIR and package-specific working dirs; actually use$temp_dir_id
for mktemp; see During build process: cp: error writing '/home/user/build/.tmp/work-XXXXXXXX: No space left on device #5502USE_TMPFS=no
disables usage of generic tmpfs mechanism (still possibly used for rootfs/image building, which is unrelated), for last-resort casestemp_dir_id
's for kernel build thank
(nowkernel_dest_install_dir
) andkd
(nowkernel_debs_temp_dir
)mktemp -d
withmktemp -d --tmpdir "${temp_dir_id}-XXXXX"
inprepare_temp_dir_in_workdir_and_schedule_cleanup()
, so we know what's using what in tmpfs