- Pull functionality back into package manager itself since the extra
indirection doesn't really buy us anything in this case, as neither
request that it handles requires a decision provider.
- Adjust pkgman and HaikuDepot accordingly.
- A subset of jobs that require a BContext don't in fact make use of the
decision provider. As such, make the default implementation usable for
those cases so one doesn't need to always create a dummy derived class.
* This has positive and negitive effects. Using the
first monitor's EDID vs the VESA EDID means DisplayPort
monitors and adaptors function. I think the benefits
outweigh the risks at this point.
* Haiku will use the native display mode of the first
monitor and set it across all attached displays.
* Please open bug reports if you notice and regressions.
* List library dependencies.
* Remove "Specific: Linux" section. I can only assume that zlib1g-dev
is/was a package for a specific distribution.
* "Configuring your build" section:
- Mention that a change of the cross-compilation tools may require
re-configuring.
- Update the configure calls as required since the package management
merge.
* "Building via Jam" section:
- Use build profiles.
- Consequently use "-q".
Fixes#9980
Since hrev44455 we save your modifier keys settings when you switch
keymaps so you could get your modifiers keys messed up and unable to
get back to normal. This Defaults button allows you to override all
that and go back to the default US-International keymap with default
modifiers so you can start with a fresh slate and set things up the
way you want.
Also moved Revert button to the left side next to the Defaults button.
We do this on other preflets, the right side is reserved for an Apply
or OK button, and, if the preflet doesn't have one, is left empty.
* Until now, only the SSID name was being used to select a certain network.
* Now, you can also specify an address.
* Unfortunately, I could not test these changes, but they are part of ticket
#10001.
* Move Volume::Exception to top level and into own files.
* Add utility class FSUtils, move Volume::RelativePath there and add a
bunch of FS utility functionality.
* Add FSTransaction, a helper class to record FS operations and revert
them.
* When activating a package we now extract the writable
files/directories it declares. The handling is not quite complete:
- We don't handle merges yet. I.e. the user will have to do that
manually for now.
- We don't propagate issues/infos regarding the writable files (e.g.
that a manual intervention is required) to the user yet.
