On Thu, Feb 24, 2011 at 7:21 AM, Dale <rdalek1...@gmail.com> wrote: > Neil Bothwick wrote: >> >> On Thu, 24 Feb 2011 07:03:06 -0600, Dale wrote: >> >> >>> >>> I just wonder if the devs have noticed how much this has grown when >>> packages with X flags are included in the system set?. Would Gnome do >>> the same? What about other GUI's? >>> >> >> What does it matter? They are only dependencies of @system, but they will >> also be dependencies of @world, because you have emerged kde-meta, so >> either way they would be on your system. >> >> There is nothing wrong with your system, it is doing exactly what you >> told it to with your USE flags, and the kde flag is not the culprit >> anyway as emerge -ep @system doesn't bring in any KDE stuff here. >> >> > > I was always under the impression that @system was supposed to be a limited > set of packages to build, including dependencies. For me, if I have a > issue, I usually start with emerge -e system to see if it helps. Since > there is some KDE stuff in there, that makes it build packages that I most > likely don't need to be rebuilt. To me, KDE is not a system package. > > It is doing what it is told but it is also doing things that it didn't use > to do even when told the same as it is being told now. It wasn't to long > ago that system was about 150 packages and didn't take that long to > recompile. Now it is over 400. If this continues, the difference between > system and world is going to be small. > > It may not be broke but it seems the system set is growing pretty quick. > > Dale
Dale, As Neil states, it has a lot to do with what you told the machine to do. I have a new, very clean, stable (not ~amd64) laptop using the kde profile. emerge -ep @system says 191 packages and I'm writing this response from that machine inside KDE so it has to be something else in your case. I posted something a couple of years ago about using -java in make.conf because I found with +java I got almost twice as many packages in @system. (Except it wasn't @system at the time) I started putting java flags in package.use and got things to work the way I wanted - easy to rebuild @system, java on the packages I really wanted java support. I suspect what you are seeing is far more in that vein than anything else. Good luck, Mark
