If you remove the status directory
you would loose the only option
to fallback / revert to previous packages.
As new packages under the
If you delete the status directory you would remove your only archived “working old” packages
you assume that worked for you.
In the internet repositories there are only the new versions available - by default.
If you want older versions you can find it locally if you have archived versions from an (any) earlier update directory on locally - at you - or you can reinstall some packages that contains in the install image.
However install image is reduced in size, so probably mentioned QT packages possibly not there as QT is not native libraries in Haiku.
They are required for 3rd party applications’ GUI elements which was built using QT - I am highly recommend to read about the User Guide, and other forum posts as well, regarding installation of Haiku and the native apps and 3rd party.
You can reinstall older versions of packages from this state directory, but I must warn you : some dependencies (packages) might newly installed at updates - you won’t find older versions of them in these state directories.
If it won’t harm your recovery - so you do not experience problem - I would suggest to leave them - and live with them - installed. It might remove automatically by reverting to older versions.
If not and you remove them manually - they might want to remove other dependencies which are belongs now to them - those can be used by other apps.
Recently I could emptied a whole Haiku install apps directory - so to damage my previous Haiku 32 bit install - as I did with kernel packages…
So you have to know precisely what you want to remove.
If you want a really clean install
you create a backup image about your Haiku install - before any update , as it is always recommended before any update/install - and in this case just restore Haiku from that image backup.
Additionally you can have a copy of your install in a VM, and update there first.
You can create clean Haiku if you have a backup copy of the virtual disk file before the any new install in the VM.
If shit happens, you just
shut your VM down,
remove the virtual drive,
copy back saved virtual drive file into the orig one using the orig disk filename on host OS.
Then when you restart the VM with the “restored” file you would have a clean, working Haiku test again.
You’ve just wasted time
once of saving virtual disk file with different name
once copy back the disk drive file onto original name.
I assure you – it will be more less painful and lesser time than a restore earlier Haiku state ( and maybe only an attempt if fails with your knowledge or experience)
on your daily system
or even in the VM itself.
Me even asked for two pkgman option – however I had not used such urging tone you had let you use yourself in your post.
Improving pkgman requires a developer with python and high Haiku knowledge about how package manager works as well … such skills as also that a newcomer must to adapt -
I would hope patiently till some developer comes with such skills or among existing developers – whom cover such requirements – have enough time and a mood as well to improve pkgman capabilities.
I asked for a
pkgman revert_all_latest installed (if possible)
a kind of ‘pkgman remove_only’
which removes only the explicit one package ( the apps e.g.), but not depencies (e.g. libraries, codecs, fonts, etc.) as well,
which ones used by other packages (apps) too.
I understand - partly - why pkgman do this, but simply annoying as well. Especially when wants to reinstall the removed stuff when you would install back only such earlier “dependencies”.
EDIT : Fix typos and add supplemental “cleaning curves”, sentences.