FS#53343 - [mkinitcpio] -s --save "Save build directory" flag does not output where the saved directory is
Attached to Project:
Arch Linux
Opened by Ceriel Jacobs (cj1) - Friday, 17 March 2017, 00:25 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 01 October 2017, 17:40 GMT
Opened by Ceriel Jacobs (cj1) - Friday, 17 March 2017, 00:25 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 01 October 2017, 17:40 GMT
|
Details
Description:
Adding the -s --save "Save build directory" flag doesn't output on console where the directory is. Not even when adding flag -v --verbose. The directory is not saved in /tmp (ls -l /tmp = total 0) Or it is a bug that the saved directory is actually not saved at all. Additional info: * mkinitcpio version 22 * config: MODULES="ehci-hcd ehci-pci" BINARIES="" FILES="/etc/modprobe.d/modprobe.conf" HOOKS="base udev autodetect modconf block filesystems keyboard fsck" COMPRESSION="lz4" COMPRESSION_OPTIONS="-9" Steps to reproduce: mkinitcpio -sp linux mkinitcpio -s -p linux mkinitcpio -sv -p linux mkinitcpio -s -v -p linux |
This task depends upon
Closed by Dave Reisner (falconindy)
Sunday, 01 October 2017, 17:40 GMT
Reason for closing: Fixed
Additional comments about closing: https://git.archlinux.org/mkinitcpio.git /commit/?id=91b212551a5066
Sunday, 01 October 2017, 17:40 GMT
Reason for closing: Fixed
Additional comments about closing: https://git.archlinux.org/mkinitcpio.git /commit/?id=91b212551a5066
$ mkinitcpio -s
==> Starting dry run: 4.10.2-1-ARCH
-> Running build hook: [base]
-> Running build hook: [systemd]
-> Running build hook: [strip]
==> Generating module dependencies
==> Dry run complete, use -g IMAGE to generate a real image
==> build directory saved in /tmp/mkinitcpio.5t1c1J
The documentation doesn't list for -s (--save) something like "This flag is incompatible with -p flag".