PKGKDE-...V-LATEST(1)

💖 PKGKDE-OVERRIDE-SC-DEV-LATEST 💖

okay bestie, welcome to section 1 of the User Contributed Perl Documentation, aka pkgkde-override-sc-dev-latest 🌸

✨ NAME ✨

pkgkde-override-sc-dev-latest — it loosens the Breaks restrictions that kde-sc-dev-latest throws at you 💅

---

🎀 SYNOPSIS 🎀

pkgkde-override-sc-dev [-bbase_version] [-vversion]

---

🦋 DESCRIPTION 🦋

so pkgkde-override-sc-dev-lastest is this little helper utility that exists for one (1) extremely specific reason: it builds you a dummy kde-sc-dev-latest package that has no Breaks field, unlike the real one which is absolutely serving cunt with the restrictions 😭

here's the lore, bestie: the original kde-sc-dev-latest package is there to force all the KDE Software Compilation modules to get built against the latest version of the KDE Development Platform modules, and it does that without you having to bump the versions of a whole bunch of build dependencies for every single KDE SC module. iconic behaviour, honestly 👑

but here's the thing — and this is the part that eats: while the original kde-sc-dev-latest is totally fine when you're building in clean chroots, the restrictions from its Breaks field can be straight up undesirable on the maintainer's system when:

• the maintainer wants to (test)build KDE module version X.Y.A against KDE Development Platform X.Y.B, where (A > B);
• the maintainer is building a new upstream version of some KDE Development Platform module on a system that already has an old version of some KDE Development Platform packages installed. for example, even if kdepimlibs does not build depend on kdebase-workspace-dev, the original kde-sc-dev-latest may still prevent kdepimlibs X.Y.A from being built on a system that has kdebase-workspace X.Y.B (where A > B) installed. rude fr fr 💀

by default, pkgkde-override-sc-dev-latest generates a dummy kde-sc-dev-latest package right there in your current working directory, based on the current "candidate" version of the original kde-sc-dev-latest (as per apt-cache policy). you can also specify a base version with the -b option ✨

the resulting dummy kde-sc-dev-latest override package will carry base_version+override as its version, unless you specify a different one with the -v option 🌈

once the package is generated, you install it like this:

# dpkg --install kde-sc-dev_<version>+override_all.deb

---

👑 OPTIONS 👑

• -bbase_version, --basever=base_version — the version of the original kde-sc-dev-latest package that you want to base an override package on. it must be available in the APT database on your system, no exceptions 🫶 you may also pass the special value latest to select the latest available version in the APT database. and if you pass priority, then the latest version with the highest priority will be selection. by default (aka when this option is not specified at all), the candidate version is selected 💖
• -vversion, --version=version — generates an override package using the version+override you specify, instead of the default base_version+override version. you're the main character, pick your own version 💅

---

🌟 AUTHOR 🌟

Modestas Vainius <modax@debian.org> 🎀

---

and that's a wrap babes ✨ this page came to you from perl v5.42.3, dated 2026-08-19 — slay, stay hydrated, and never forget to read the fine print 💜