The last part of fixing #9399.
Note: Hopefully this is 'OK'. `jam -q catkeys` and `jam -q catalogs` ran
without issue. Running FirstBootPrompt managed to use up the compiled catalogs.
The previous name is no longer applicable, as *BootPrompt is now launched on
the first boot of writable medium (e.g., USB thumb drive and hard drives).
Fixes part of #9399.
Notes:
* BootPrompt.rdef may have lost its history.
* The renaming was done with the following command:
git mv src/apps/readonlybootprompt src/apps/firstbootprompt
That file will exist on every read-only media, first boot of writable images
(usb,vmdk), and (if installing directly to partition via the build system or a
mounted image file) hard disk.
The last scenario (of installing directly to hard disk through the build system
or mounted image file) may not be ideal, but it generally tends to be an
advanced installation method. Additionally, it will occur only on first boot.
Fixes#8945.
* The regex for the OpenSSL package name variable didn't catch up
with the changed file which checked for the gcc version.
* Webkit was declared using a custom variable that wasn't grepped for.
The ls command, uses blue color for directories. For a directory that
has write permission for others, it uses green highlighting while
displaying the directory name. However, blue text and green highlight
is difficult to read.
The patch keeps the text color as blue and changes the highlight to
yellow.
Signed-off-by: Jérôme Duval <jerome.duval@gmail.com>
All grep versions have the ability to display a colored
output. The patch turns on coloring in auto mode.
Signed-off-by: Jérôme Duval <jerome.duval@gmail.com>
ls --color emits the color code irrespective of whether it is being
attached to terminal or not. Which might result in color codes being
added to file upon redirection.
auto option with ls --color emits the color codes only the output is
attached to terminal, otherwise the colors are turned off.
Fixes#8993.
Signed-off-by: Ryan Leavengood <leavengood@gmail.com>
