On 10/11/2011 11:50 AM, Francisco Blas Izquierdo Riera (klondike) wrote: > Hi, > > Today I have found that build dependencies are left in the system but > won't be upgraded when running emerge -vauD1 world. > This can be inconvenient since security issues fixed in those left over > packages won't be applied properly. > So, is there any reason for this behaviour?
1) It's a waste of time to build/update packages that won't be used for anything. That's what --with-bdeps=y. If you plan to use these packages for something, then you should add them to world or add --with-bdeps=y to EMERGE_DEFAULT_OPTS so that they'll update automatically. 2) Aside from being a waste of resources, if we enabled --with-bdeps=y by default for update actions then to would cause unwanted results for people who use binary packages and don't expect the build-time deps to get pulled in. > Shouldn't build dependencies > either be cleaned with --depclean after building This is another waste of resources, since you'll have to install them again the next time that you need them. However, you are free to use --with-bdeps=n with --depclean if it suits you. One size does not fit all, so that's why we have options. > or be upgraded to avoid > possible issues? Again, if you plan to use these packages for something, then you should add them to world or add --with-bdeps=y to EMERGE_DEFAULT_OPTS so that they'll update automatically. Again, you've got choices and what suits you doesn't necessarily suit everyone else. Personally, I like to set EMERGE_DEFAULT_OPTS="--with-bdeps=y" because like to know that all the build deps are at their latest versions in case I decide to rebuild some random package. -- Thanks, Zac
