Exercise 3: Why apt/dnf Tolerate Partial Upgrades but pacman Doesn't — Possible Solution
====================================================================

WHAT THIS CHAPTER SAYS ABOUT apt AND dnf SPECIFICALLY
------------------------------
Per this chapter, "apt and dnf both resolve dependencies against
repository metadata and are relatively tolerant of partial upgrades -
installing one new package without a full system update generally
works fine on either."

WHY THIS TOLERANCE IS POSSIBLE ON POINT-RELEASE SYSTEMS
------------------------------
Debian and Fedora are both point-release distributions, per Chapters 2
and 3 - within one release (one frozen Debian Stable version, or one
Fedora version), package versions and their interdependencies are
managed together as a coherent set for that release's own lifetime.
Installing one new package from within that same release's repository
pool is drawing from a set of packages already designed to work
together, so a single new install rarely conflicts badly with what's
already there.

WHAT THIS CHAPTER SAYS ABOUT pacman, AND WHY IT'S GENUINELY DIFFERENT
------------------------------
Per this chapter's own warn-box, "on a rolling-release system, installed
packages and their shared libraries are tightly version-coupled -
installing a single new package... without first fully syncing and
upgrading the entire system... can pull in a package built against
library versions newer than what's currently installed." Because Arch
has no discrete release boundary at all (per Chapter 4), the repository
is a single, ever-advancing stream rather than a coherent, frozen set -
a package installed today may already assume newer companion libraries
than what a system last updated even a short time ago actually has.

WHY THIS DIFFERENCE TRACES DIRECTLY BACK TO THE RELEASE MODEL
------------------------------
The tolerance difference isn't really about apt/dnf being "smarter"
package managers than pacman - it's a direct consequence of Chapter 4's
own release-model distinction. Point-release systems have a stable,
matched baseline to install additional packages against; a rolling-
release system has no such fixed baseline, so any partial update risks
mixing packages from different points along that continuous stream.

WHY THIS WORKS AS AN ANSWER
------------------------------
It restates this chapter's own characterization of apt/dnf's tolerance
and pacman's own strictness, and explains both by tracing them directly
back to the point-release-vs-rolling-release distinction established in
Chapters 2-4, rather than treating the difference as an arbitrary
design choice between tools.