I don't have a printer, and never expect to have one, so I try to
remove any print related packages,
and I'm currently targetting x11-proto/printproto.
This package is conditional on the "xprint" USE flag in
x11-base/xorg-server which is OFF in emerge --info.
I recenly installed 64 bit firefox (thought I'd give it another go,
not working so hot that that's another rant) which includes
www-client/mozilla-launcher which has a hard dependency on
x11-apps/xdpyinfo.
x11-apps/xdpyinfo has a hard dependency on x11-proto/printproto
despite the code being conditional on xprint via the config
HAVE_X11_EXTENSIONS_PRINT_H, which will always be
true since the ebuild pulls it in.
Now I think there is a bug in the x11-apps/xdpyinfo ebuild. I changed
xdpyinfo-1.0.1.ebuild
34c34
< xprint? ( x11-proto/printproto )"
---
x11-proto/printproto"
# ebuild xdpyinfo-1.0.1.ebuild digest
and tested it
# xdpyinfo > ~/tmp/xdpyinfo-before
# emerge -aC x11-proto/printproto
# emerge -a1 x11-apps/xdpyinfo
# xdpyinfo > ~/tmp/xdpyinfo-after
# diff ~/tmp/xdpyinfo-before ~/tmp/xdpyinfo-after
54d53
< print screen: no
The compile was clean, the baseline/regression test (rudimentary) worked well.
So my question is: is this enough to submit as a bug/feature request?
I ask because I've submitted quite a few bugs and gotten unpolite
responses on occassion, left out obvious information, and generally
looked like the dumb user I'm tring not to be.
--
[email protected] mailing list
