CUPT_VS_APT(5)

💖 NAME 💖

cupt_vs_apt — bestie, this is the whole rundown of the things Cupt and APT do differently. like, the receipts. the iceberg. the "wait why does this not work the same" doc. 🦋

---

✨ FEATURE SETS ✨

okay so if you wanna know which one wins at what, go peek at the "Disadvantages and advantages" section over in cupt_tutorial. that's where the full tea is spilled. 👑

---

🔥 DIFFERENT BEHAVIOR 🔥

🌸 Configuration 🌸

here's where the default vibes diverge, no cap:

• apt::cache::allversions — defaults to 0, not 1 like it does in apt-cache. so yeah, different starting energy. 🙈
• gpgv::trustedkeyring — defaults to /var/lib/cupt/trusted.gpg. that's the keyring home, periodt. 🔑
• so you wanna put your compression types in priority order? that's the cupt::update::compression-types option, not acquire::compression-types. don't mix them up bestie, they are NOT the same. 💅
• and if you're picking which localizations of the repository indexes you want, use cupt::languages::indexes, not acquire::languages. same energy, different name. 🌈

⭐ Pinning ⭐

the pinning situation, and listen closely:

• the difference between specific and general pin types? yeah… not supported. it's giving "we don't do that here". 😭
• by default, an additional pin priority penalty gets applied to NotAutomatic releases. and if you wanna know more about that whole thing, go look at the cupt::cache::pin::addendums::not-automatic option. 🎀

---

💀 heads up: those two pinning quirks are the real ones. don't assume APT's exact semantics carry over, because they lowkey don't.

---

and that's the doc, babe 💖 written up with perl v5.38.2, dated 2024-03-31, and you can find it chillin' in the User Contributed Perl Documentation. slay, go configure something. 🫶✨