grub fails if ${ROOT}/boot does not exist: # mkdir tmp # USE=-* ROOT=tmp emerge -avt grub ... snipp ... >>> Failed to install sys-boot/grub-0.97-r9 to /root/tmp/, Log file: >>> '/var/log/portage/sys-boot:grub-0.97-r9:20090309-130257.log' * Messages for package sys-boot/grub-0.97-r9 merged to /root/tmp/: * * To avoid automounting and autoinstalling with /boot, * just export the DONT_MOUNT_BOOT variable. * * * ERROR: sys-boot/grub-0.97-r9 failed. * Call stack: * ebuild.sh, line 49: Called pkg_postinst * environment, line 2766: Called setup_boot_dir '/root/tmp//boot' * environment, line 2983: Called die * The specific snippet of code: * [[ ! -e ${dir} ]] && die "${dir} does not exist!"; * The die message: * /root/tmp//boot does not exist! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/sys-boot:grub-0.97-r9:20090309-130257.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-boot/grub-0.97-r9/temp/environment'. * * Regenerating GNU info directory index... * Processed 3 info files. I expect the ebuild to create the dir if it doesn't exist. Like it does for every other dir it is installing files into. Please explain if this behaivor is intended. Thanks
Created attachment 184452 [details] grub-create-boot-dir.patch Proposed patch to create dir instead of failing if ${ROOT}/boot doesn't exist.
Reassigning to base-system herd.
InCVS.
