partial upgrades are confusing, and man page does not explain what upgrade means about pkgin

[gdt]

Specifically, the man page does not explain that if for installed packages A and B, with B depending on A, that if A is in the repo and B is not, that will likely result with (old) B having an incorrect dependency A, which if the ABI is different will cause B to fail. It also doesn't give a hint of how a user might see if this is the case before upgrading.

[jperkin]

Partial upgrades via pkgin upgrade were deprecated in 0.13.0 and since then pkgin upgrade replaces pkgin full-upgrade. Hopefully the current documentation makes it clear that this will always perform a full upgrade.

Partial upgrades via pkgin install (i.e. operating on an updated repository for selected packages without before performing pkgin upgrade first) historically didn't work very well, but with recent changes in pkgin will now at least consider all affected packages. I'll close this issue once those changes have been released in the next version.

Issues around packages no longer being available in the repository will be dealt with in #100.