I did search for this (and couldn't find it). It seems hard to believe that no one has reported it before. Just installed the portage update. While I like the idea of getting rid of the automatic use flags for installed packages by default, I did notice this: $ emerge -pv tar These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] app-arch/tar-1.15.1-r1 USE="nls -build -bzip2* -static" 0 kB Building tar without bzip2 support does not seems like "a good thing." Before, with bzip2 as part of the system profile, this flag got enabled. Now, I worry that some people will bork their machines the next time they emerge -e.
The use flag doesn't appear to do anything useful, except for adding a dependency that's in profiles/base/packages anyway. Why is it there?
read cvs history: http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-apps/tar/tar-1.13.25-r2.ebuild?hideattic=0&r1=1.6&r2=1.7
(In reply to comment #2) > read cvs history: > http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-apps/tar/tar-1.13.25-r2.ebuild?hideattic=0&r1=1.6&r2=1.7 > Hmmm? I'm probably dense but I don't get it. The flag still doesn't do anything useful, neither in the revision linked above, nor in the current one.
++what is the usefulness of this Mike? Other then to possibly break systems if bzip2 gets dropped off the base system.
removed a bunch of stuff from the ebuild
