#
5d55f327 |
|
17-Apr-2014 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
packagefs: Initial support for booting into old states If an old state is specified via mount parameters we load the packages as specified in its activated-packages file. The interface for the package daemon, the package daemon itself, and the package kit are still to be adjusted, so ATM some PM components might be a bit confused when an old state was booted.
|
#
dff8d2ea |
|
17-Feb-2014 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
packagefs: Package: Use PackagesDirectory directly ... instead of Volume. Necessary to support using packages from different directories.
|
#
aeb6fc9e |
|
10-Feb-2014 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
packagefs: Move Volume::PackagesDirectory to top level Also make it a BReferenceable and fix Volume::fPackagesDirectory leak.
|
#
3a7e0b00 |
|
19-Nov-2013 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
packagefs: Support blacklisting entries in packages In each installation location, it is now possible to create a settings file "packages" that allows to blacklist entries contained in packages. The format is: Package <package name> { EntryBlacklist { <entry path> ... } } ... <package name> is the base name (no version) of the respective package (e.g. "haiku"), <entry path> is an installation location relative path (e.g. "add-ons/Translators/FooTranslator"). Blacklisted entries will be ignored by packagefs, i.e. they won't appear in the file system. This addresses the issue that it may be necessary to remove a problematic file (e.g. driver, add-on, or library), which would otherwise require editing the containing package file. The settings file is not not "live". Changes take effect only after reboot (respectively when remounting the concerned packagefs volume).
|
#
d07c930c |
|
11-May-2013 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
packagefs: Share string instances globally Introduce a class String which refers to shared private data that is registered in a global hash table (in class StringPool) and use the class consequently. This eliminates duplicate allocations for the same string and also speeds up tests for equality. There's quite a bit overhead for the management structures (apparently even more than for the string data itself), but due to almost all strings being used multiple times this still almost halves the memory usage for string data.
|
#
1e7416d9 |
|
11-May-2013 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
packagefs: Organize sources into subdirectories
|
#
5d55f327edfafcb9d3a61e7132c67ddda2f52cba |
|
17-Apr-2014 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
packagefs: Initial support for booting into old states If an old state is specified via mount parameters we load the packages as specified in its activated-packages file. The interface for the package daemon, the package daemon itself, and the package kit are still to be adjusted, so ATM some PM components might be a bit confused when an old state was booted.
|
#
dff8d2ea22e081f2369f0e0967c812123d27cbad |
|
17-Feb-2014 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
packagefs: Package: Use PackagesDirectory directly ... instead of Volume. Necessary to support using packages from different directories.
|
#
aeb6fc9eca1b3684f835b648e44ca877e29296ab |
|
10-Feb-2014 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
packagefs: Move Volume::PackagesDirectory to top level Also make it a BReferenceable and fix Volume::fPackagesDirectory leak.
|
#
3a7e0b00147f7a33bc52cb75a56bde8d9652d92a |
|
19-Nov-2013 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
packagefs: Support blacklisting entries in packages In each installation location, it is now possible to create a settings file "packages" that allows to blacklist entries contained in packages. The format is: Package <package name> { EntryBlacklist { <entry path> ... } } ... <package name> is the base name (no version) of the respective package (e.g. "haiku"), <entry path> is an installation location relative path (e.g. "add-ons/Translators/FooTranslator"). Blacklisted entries will be ignored by packagefs, i.e. they won't appear in the file system. This addresses the issue that it may be necessary to remove a problematic file (e.g. driver, add-on, or library), which would otherwise require editing the containing package file. The settings file is not not "live". Changes take effect only after reboot (respectively when remounting the concerned packagefs volume).
|
#
d07c930c1eb710289922edd3abf5244c259a86c6 |
|
11-May-2013 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
packagefs: Share string instances globally Introduce a class String which refers to shared private data that is registered in a global hash table (in class StringPool) and use the class consequently. This eliminates duplicate allocations for the same string and also speeds up tests for equality. There's quite a bit overhead for the management structures (apparently even more than for the string data itself), but due to almost all strings being used multiple times this still almost halves the memory usage for string data.
|
#
1e7416d9b3846396e2f7d6552e37d72664cd6853 |
|
11-May-2013 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
packagefs: Organize sources into subdirectories
|