[haiku-bugs] Re: [Haiku] #6027: Execute some of the first boot scripts as part of the build process
- From: "bonefish" <trac@xxxxxxxxxxxx>
- Date: Tue, 18 May 2010 18:12:59 -0000
#6027: Execute some of the first boot scripts as part of the build process
--------------------------+-------------------------------------------------
Reporter: bonefish | Owner: bonefish
Type: enhancement | Status: new
Priority: normal | Milestone: R1
Component: Build System | Version: R1/Development
Keywords: | Platform: All
Blockedby: | Patch: 0
Blocking: |
--------------------------+-------------------------------------------------
Comment(by bonefish):
Replying to [comment:1 andreasf]:
> Why can't the equivalent of
[browser:haiku/trunk/data/common/boot/post_install/mime_update.sh@36614
mime_update.sh] be done from the build process?
It could be done, it's just a way more complicated solution. What I
proposed can be implemented in a few minutes plus testing.
> Haiku should know where it just created its {{{B_DESKTOP_DIRECTORY}}}
and {{{B_SYSTEM_DIRECTORY}}}, thus no need for `finddir`. So, is it the
`query` call?
The main issue is that it all has to happen in the image. ATM the only way
to access the image is via the shell-like commands the bfs_shell provides.
Something like `query` could be added relatively easily, but `mimeset` is
non-trivial, since under Haiku its main work is done by the registrar.
Anyway, I guess the cleanest solution -- one that would work for all
installation targets -- would be to install everything in a temporary
directory first, perform all post installation tasks, and then just copy
it to the blank image, create an ISO image from it, or copy it to the
installation directory. An obviously nice advantage is that it minimizes
the installation target specific interface to a single "copy to target"
function.
--
Ticket URL: <http://dev.haiku-os.org/ticket/6027#comment:2>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
