Split out of https://invent.kde.org/kde-linux/kde-linux/-/issues/424 ## Pros - Status quo; no additional work required to make it happen - Minimally-patched packages minimize work required to undo patches we don't benefit from - Arch Wiki fully applies to the base distro, providing great documentation for how to build or change basically anything we want - Build and debug files included in packages; no need to manually add them later - Rolling release model means great support for cutting-edge hardware, and dependencies are always new enough for git master KDE software or anything else ## Cons - "Latest is not always greatest"; UX breakage from upstream that passes through Arch requires us to do all the QA - Packaging instability: https://invent.kde.org/kde-linux/kde-linux-packages/-/issues/9 - With no stable releases, any package combination we freeze on may need patching by us - Many packages that we want [are only in AUR](https://invent.kde.org/kde-linux/kde-linux/-/issues?sort=created_date&state=opened&label_name%5B%5D=Needs%20packaging&first_page_size=100), which is dangerous and has flaky infrastructure - Doesn't package a version of ffmpeg without patent-encumbered codecs; this is a DIY affair or else you have to use gstreamer - No package changelogs we can parse and send along to the user in Discover Feel free to discuss in the comments, and suggest more pros or cons.