3 ms·
It's funny how you complain about Arch being "needlessly complicated", then suggesting to use Debian instead. I'm building packages for Arch all the time (mostl
by majewsky 9y ago
It's funny how you complain about Arch being "needlessly complicated", then suggesting to use Debian instead. I'm building packages for Arch all the time (mostly for personal use). The one time I tried to build a Debian package, I gave up after spending multiple hours of going through all the ceremony that's involved in that.
I'm not saying that Debian is hopelessly overengineered. All the complexity is there for a reason, because Debian strives to cover 100% of what everyone needs. Arch is content with achieving 95%, if it means that you can avoid a huge part of the complexity that comes from catching the last 5%.
For example, some Debian packages use a dialog system to set themselves up during installation. Arch avoids that complexity and instead expects the user to read the wiki on how to configure the application in question.
- btschaegg 9y agoThis. Plus, makepkg is awesome. If, say, I need a specific font installed, I have no trouble with whipping out a short PKGBUILD that downlads, checks, and installs the files - providing me with the option to manage it using Pacman. Its simplicity seems so essential to me that I can't imagine why there are so few distros providing tools like it.