OK, I know it's not fashionable to actually read the documentation =:^( , but... The global use description for use=minimal is (correctly, IMO) designed to warn people off of setting it in make.conf -- it's a flag that should be set for individual packages, not globally. As such, packages that iuse=minimal normally also set their own description of what use=minimal does for that specific package. Unfortunately, not only does the new xinit-1.2.0-r1 fail to set a use=mimimal description, it use-defaults it to on. Now any gentoo using sysadmin worth his salt is going to be hearing all sorts of alarm bells ringing if he sees a use=minimal that he didn't deliberately set show up, and will certainly be investigating it. Unfortunately, not only does there appear to be no individual metadata description of the flag for this package, but emerge -pl (from former ~arch 1.0.8-r10) doesn't give any hint about it in the changelog, either. I had to actually go look in the ebuild itself to see what on earth it was doing with iuse=+minimal. That answered my question, but where's the proper package use flag documentation, and why don't I see anything in the changelog about it being use-defaulted to on, either? (FWIW, the two changelog entries matching minimal are back in 2006, version 1.0.2-rX, long before use-defaults IIRC, and I know it hasn't been enabled by default until now, so there should be /something/ documenting the change in the changelog, but I can't see it if there is.) As I said, I know it's not fashionable to read the documentation, but sysadmins aren't known to care so much about fashion after all... =;^) ... and some of us /do/ have alarm bells going off when we see a change like this and want to know what's going on.
Do you _really_ have to always write so much? Get to the point... And as for the documentation, we'll add a small blurb, it's indeed a good suggestion. Thanks
Fixed in portage. Thanks
Thank you, too. =:^) (Guess I was a bit long-winded, there. Sorry.)
