Forgive my boldness. But since we are about to move on to a new release of VL and are looking at angles to give VL the edge. I thought now might be the time to speak up before we are too deep into it.
I've wondered why the KDE packages are packaged in bulk rather then breaking them down to only include the application the user actually wants. I know it's practical and less complicated to package according to the way KDE sends out their source code, but if a user wants one particular application that is within a package, they have no choice but to install the rest of the bloat as well. I know I've run in to that over and over again, and is part of the reason I choose not to use KDE. I do not like having to scan through unused menu entries to launch a needed app.
Breaking things down would assist our dial up users, those with limited disk space and VL Standard users wanting a minimal KDE install.
It doesn't seem to be the Slackware way as far as I can see, but I think we are "Slackware Improved" why not improve it a bit more?
Building the KDE packages in this way really wouldn't be so hard and I would be more than willing to shift my package building time in that direction if we were to accept my proposal. We would just need to discuss and come up with a standard of which packages would be packaged separately and what ones were packaged in bulk.
Have any thoughts on this?