[prev in list] [next in list] [prev in thread] [next in thread] 

List:       haiku-bugs
Subject:    [haiku-bugs] Re: [Haiku] #18396: mime_db entry pointing to non-existing file prevents replicant from
From:       "Haiku" <trac () haiku-os ! org>
Date:       2023-04-30 12:16:27
Message-ID: 061.c8fb4f486919cc794957c2d732b69cac () haiku-os ! org
[Download RAW message or body]

--===============3335709951706516564==
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

#18396: mime_db entry pointing to non-existing file prevents replicant from=
 working
--------------------------+----------------------------
  Reporter:  pulkomandy   |      Owner:  nobody
      Type:  enhancement  |     Status:  new
  Priority:  normal       |  Milestone:  Unscheduled
 Component:  - General    |    Version:  R1/Development
Resolution:               |   Keywords:
Blocked By:               |   Blocking:
  Platform:  All          |
--------------------------+----------------------------
Comment (by bipolar):

 > On initial instanciation, maybe the message could include a node_ref to
 the original executable, to make sure the right thing is instanciated?

 That sounds like it could help/solve the case of testing custom builds of
 OS provided replicants. Am I too off?

 I'm thinking in the case of AboutSystem, for example, where to test my
 changes, I had to blacklist app/AboutSystem at boot time (lesson learnt
 the hard way :-D).
-- =

Ticket URL: <https://dev.haiku-os.org/ticket/18396#comment:1>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
--===============3335709951706516564==--

[prev in list] [next in list] [prev in thread] [next in thread]