I have always regarded ArchLinux as a pure Linux distribution. We need to stick to how upstream vanilla applications act as much as possible. Splitting packages is inherently evil. It should only be done when there is an absolute need. It is only acceptable to do so when there is a case where the package maintainer doesn't want to force dependencies on people, for example in gstreamer plugins. Even splitting gcc was pushing it a bit in my opinion but I trust it was done for a very good reason. It was in fact done elegantly so there's not problem here.
But splitting a package into aaa-bin, aaa-dev, aaa-data, aaa-doc and aaa-lib is bad. There's a reason "Arch Linux is a lightweight and flexible linux distribution that tries to Keep It Simple." and we should take pride in that. Yes, some package such as KDE should be split up, but that should ONLY be done upstream. We should package 'KDE' and not 'ArchKDE'. There's also a well maintained KDEmod. But otherwise, please don't make it a habit of splitting up packages unless there is a major reason. What next, port debconf to pacman?
signature.asc
Description: This is a digitally signed message part
_______________________________________________ arch mailing list [email protected] http://archlinux.org/mailman/listinfo/arch
