#12564: pkgman install *un*installs the package (if passed a local hpkg, no
problem
with remote hpkr's)
--------------------------------+----------------------------
Reporter: ttcoder | Owner: bonefish
Type: enhancement | Status: new
Priority: normal | Milestone: R1
Component: Kits/Package Kit | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
--------------------------------+----------------------------
Comment (by ttcoder):
No pressure, can wait until the upcoming beta1 ..etc cycle or later -- the
whole packaging system thing has made our life much easier already, but
I'm always greedy for more silky-smoothness :-)
Forgot to mention, the "old state" directory does /not/ contain anything
else than the old activated-packages text file.. I would have expected it
to contain an instance of the lnlauncher.hpkg file; yet the only such
copies are the 1) source hpkg file on Desktop, and 2) the (now
deactivated) one in /system/packages
I could check the mod timestamp of the latter to determine if it's the old
one (that thus failed to move?) or the new one
Also out of curiosity I looked at [http://cgit.haiku-
os.org/haiku/tree/src/servers/package/CommitTransactionHandler.cpp?id=8c63feccbb00279f501ac0f79b38f053e65a316d#n1662
ChangePackageActivation] to see what would happen if two packages of the
same basename and version number were passed within the
`packagesToActivate` argument and the `packagesToDeactivate` argument..
But in that case the code clearly [http://cgit.haiku-
os.org/haiku/tree/src/servers/package/CommitTransactionHandler.cpp?id=8c63feccbb00279f501ac0f79b38f053e65a316d#n1623
adds it as activated]. So if anything, this all indicates that the
`packagesToActivate` variable does /not/ contain the lnlauncher hpkg I
guess
--
Ticket URL: <https://dev.haiku-os.org/ticket/12564#comment:3>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.
