#10041: [PM] cannot override 'system' driver -------------------------+----------------------------------- Reporter: ttcoder | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1/Package Management Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: All -------------------------+----------------------------------- Comment (by ttcoder): Thinking of it more.. There might be more to this discussion before closing the ticket. What if I have a system component (e.g. driver, app, anything) override, that I want to distribute with my app. Contrarily to things that are under my control (e.g. upgrading to successive versions of my apps), I cannot predict the mod-time of the component I want to override: if the client has a recent nightly of Haiku, more recent than the nightly I use for development, all the components inside will have a higher mod-time than the overriden components I'm packaging. To ensure proper override, I could do {{{touch --date=January,1,2099 <file>}}} on all concerned 'overrides' and be good for close to a century, but that's a bit kludgy... But maybe the PM philosophy is that overriding the system is discouraged, and so it should only be done with the above 'touch' rather than made easy with an explicit mechanism? Just food for thought.. Me I'm happy as long as there is an easy workaround anyway, and 'touch' is easy indeed. -- Ticket URL: <http://dev.haiku-os.org/ticket/10041#comment:13> Haiku <http://dev.haiku-os.org> Haiku - the operating system.