how do you explain this? # emerge -uDNvp world These are the packages that would be merged, in order: Calculating world dependencies... done! [ebuild R ] app-editors/emacs-cvs-23.0.0-r6 USE="X alsa gif jpeg png spell tiff xft xpm* -Xaw3d -gtk -gzip-el -hesiod -lesstif -motif -sound -source -toolkit-scroll-bars" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB # euse -i xpm global use flags (searching: xpm) ************************************************************ [- ] xpm - Adds support for XPM graphics format local use flags (searching: xpm) ************************************************************ no matching entries found # USE=-xpm emerge -uDNvp world These are the packages that would be merged, in order: Calculating world dependencies... done! Total: 0 packages, Size of downloads: 0 kB # USE=xpm emerge -uDNvp world These are the packages that would be merged, in order: Calculating world dependencies... done! [ebuild R ] media-libs/gd-2.0.34 USE="jpeg png truetype xpm* -fontconfig" 0 kB [ebuild R ] app-editors/emacs-cvs-23.0.0-r6 USE="X alsa gif jpeg png spell tiff xft xpm* -Xaw3d -gtk -gzip-el -hesiod -lesstif -motif -sound -source -toolkit-scroll-bars" 0 kB [ebuild R ] dev-lang/php-5.2.2-r1 USE="apache2 berkdb bzip2 cli crypt filter gdbm iconv imap ipv6 ldap mysql ncurses nls pcre postgres readline reflection session snmp spell spl sqlite ssl truetype unicode xml xpm* zlib -adabas -bcmath -birdstep -calendar -cdb -cgi -cjk -concurrentmodphp -ctype -curl -curlwrappers -db2 -dbase -dbmaker -debug -discard-path -doc -empress -empress-bcs -esoob -exif -fastbuild -fdftk -firebird -flatfile -force-cgi-redirect -frontbase -ftp -gd -gd-external -gmp -hash -inifile -interbase -iodbc -java-external -json -kerberos -ldap-sasl -libedit -mcve -mhash -msql -mssql -mysqli -oci8 -oci8-instant-client -odbc -pcntl -pdo -pdo-external -pic -posix -qdbm -recode -sapdb -sharedext -sharedmem -simplexml -soap -sockets -solid -suhosin -sybase -sybase-ct -sysvipc -threads -tidy -tokenizer -wddx -xmlreader -xmlrpc -xmlwriter -xsl -yaz -zip -zip-external" 0 kB Total: 3 packages (3 reinstalls), Size of downloads: 0 kB # why does portage thinks that such xpm flag get set only for emacs-cvs? I see nothing apparent in the ebuild. Reproducible: Always
It comes from package.use in the base profile.
$ cat /usr/portage/profiles/base/package.use # This file requires >=portage-2.1.2 (see bug #61732) # Strongly recommended, otherwise all logos, icons, etc. appear in b/w. app-editors/emacs-cvs xpm
Reopening.
Ah ok I didn't notice that file. Really I didn't imagine somebody really cared about xpm and so I assumed it had to be a glitch in portage and not some developer turning it on. Personally I cannot care less about xpm, while I couldn't live w/o xft with subpix, if it was up to me that line would look like: app-editors/emacs-cvs xtf Actually I enabled xtf in make.conf just in case ;)
(In reply to comment #0) > [ebuild R ] app-editors/emacs-cvs-23.0.0-r6 USE="X alsa gif jpeg png > spell tiff xft xpm* -Xaw3d -gtk -gzip-el -hesiod -lesstif -motif -sound > -source -toolkit-scroll-bars" 0 kB Why do you regard USE=xpm as an unsuitable default for emacs-cvs? With USE=-xpm the splash screen and all icons inside Emacs will be displayed in black and white. There may be valid reasons to ask for this, but I am curious to hear them.
never mind, we clearly have different usage of it. My emacs window is like xterm. I would never display anything that isn't a subpix antialised font in such a window. I even dropped the gtk linkage that only wasted some ram in shared libs. About the splash screen this is my preferred default in .emacs (setq inhibit-startup-message t) But I really don't care less what's the default is, sure somebody will like that splash screen if they leave it there! Just that xpm thing really made me think something was wrong sorry.
(In reply to comment #6) > My emacs window is like xterm. I would never display anything that isn't a > subpix antialised font in such a window. Please note that the xft flag is only supported by emacs-cvs-23.0.0*, i.e. the unicode-2 branch, but not by the to be released Emacs 22 series. So I believe it would be unsuitable to provide a global default for xft at this stage. > But I really don't care less what's the default is, sure somebody will like > that splash screen if they leave it there! Just that xpm thing really made me > think something was wrong sorry. Reopening for proper closing then.
RESOLVED NOTABUG
> Please note that the xft flag is only supported by emacs-cvs-23.0.0*, i.e. > the unicode-2 branch, but not by the to be released Emacs 22 series. So I > believe it would be unsuitable to provide a global default for xft at > this stage. Yes, at least for anything older than 23.0.0*. I wonder why they don't backport the xft stuff to the to be released 22. I'm never going to use 22, either 21 or 23. And the only reason to use 21 is if 23 starts badly corrupting stuff (which didn't happen yet). 22 is just irrelevant as far as I'm concerned. Thanks everyone for the help.
