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>
This adds some of the development packages for x86_64. All of the
DevelopmentBase packages (gcc, make, jam, bison, flex, m4, mkdepend)
have been built and uploaded.
- When an Identify/Force Identify request is made in Tracker, if the target
is a link, resolve it to its destination first. Fixes#8858.
- Have mime_update.sh explicitly mimeset the welcome/user guide scripts.
Some preference apps, mount_server and AboutSystem. Removed the check
for x86_64 in the boot script, the normal path through the script will
work now. Also removed a temporary hack to workaround AboutSystem not
being there in build_haiku_image.
The boot script now launches consoled instead if app_server does not
exist, so there is now an interactive Bash prompt! libbe requires ICU,
which is an optional package, so I've built the packages and they've
been uploaded to haiku-files.org (thanks umccullough).
As the downloadable files are now hosted on haiku-files.org and the user is
presented the Intel license at the beginning of the script, the function
OpenIntelFirmwareWebpage is unneeded.
In previous, it was still working as I was more interested into != 0 than
exact count. Still, for clarity sake, I add -l to get the actual count.
Thanks Axel.
The bash script tried to verify the existence of a file,
but there were several fils fitting the wildcard expression.
So, [ -e .../*gcc ]; was interpreted as if it had too many
arguments. Replaced that expression by a count of files.
Fixes#8493.
Replace the leaf bitmap with a non-cutoff version derived from the
'data/artwork/Haiku Leaf' file. So, when icon size is > 16 the full
deskbar leaf is shown without the bottom cut-off. It should look
pretty much identical at 16x16 and in vertical mode at any icon size.
Also add a deskbar_leaf.png file to the data/artwork directory
although I didn't use that file in Deskbar, instead I embed an
archive bitmap into icons.h. I got rid of icon-freelogo.rdef and
icons_logo.h.
