Unified · Split
| @@ -208,8 +208,8 @@ rm -rf "$ROOTFS/var/cache/*" 2>/dev/null · 207 unmodified lines | ||
| 208 | 208 | |
| 209 | 209 | # Finally we can compress the tarball, the name will include the |
| 210 | 210 | # architecture and the date on which the tarball was built. |
| 211 | −tarball=${FILENAME-void-${XBPS_TARGET_ARCH}-ROOTFS-$(date '+%Y%m%d').tar.xz} | |
| 212 | −run_cmd "tar -cp --posix --xattrs -C $ROOTFS . | xz -T${COMPRESSOR_THREADS:-0} -9 > $tarball " | |
| 211 | +: "${FILENAME:=void-${XBPS_TARGET_ARCH}-ROOTFS-$(date '+%Y%m%d').tar.xz}" | |
| 212 | +run_cmd "tar -cp --posix --xattrs -C $ROOTFS . | xz -T${COMPRESSOR_THREADS:-0} -9 > $FILENAME " | |
| 213 | 213 | |
| 214 | 214 | # Now that we have the tarball we don't need the rootfs anymore, so we |
| 215 | 215 | # can get rid of it. |
| @@ -219,4 +219,4 @@ rm -rf "$ROOTFS" · 3 unmodified lines | ||
| 219 | 219 | # this succeeded. This also ensures that there's something visible |
| 220 | 220 | # that the user can look for at the end of the script, which can make |
| 221 | 221 | # it easier to see what's going on if something above failed. |
| 222 | −info_msg "Successfully created $tarball ($XBPS_TARGET_ARCH)" | |
| 222 | +info_msg "Successfully created $FILENAME ($XBPS_TARGET_ARCH)" | |