On my amd64 box, splashutils emerged with fbcondecor although its not in my make.conf, on x86 it did not and required manual addition to make.conf. To me, it should be enabled by default on all arches, it makes for confusion. If someone is emerging splashutils, they will almost certainly be doing it because they want a framebuffer splash. Reproducible: Always
Please, drop the double spacing, it's extremely annoying.
What do you mean by emerged with fbcondecor? While I fully agree that if someone is emerging splashutils, they probably want a framebuffer splash, I do not agree that they would necessarily want the functionality provided by fbcondecor.
Sorry about the double spacing What I mean is that I was having problems after upgrading 2 boxes to testing, one ~amd64, the other ~x86. The amd64 box upgraded and splash worked with no changes from me. Splashutils emerged with use flag fbcondecor without having that use flag in my make.conf. On the x86 box, I immediately noticed that upon reboot, verbose splash theme wasn't working. At first I thought some library got screwed up in the upgrade but after a complete reemerge of my system, still no verbose splash. No I started digging and finally realized that the problem was that splashutils emerged without the fbcondecor use flag on that box. After re-emerging splashutils with fbcondecor use flag I then had verbose splash again. If its necessary for either verbose or silent splashes to work properly, I believe that it should be enabled by default and leave it to people to disable if they really don't want it.
(In reply to comment #3) > changes from me. Splashutils emerged with use flag fbcondecor without having > that use flag in my make.conf. On the x86 box, I immediately noticed that upon So, basically you're saying, that even though you don't have fbcondecor listed in make.conf, if you do `emerge -pv splashutils`, you can see that the flag is enabled?
On the amd64 box, after doing emerge --update --deep --newuse world with ~amd64 accept keywords in my make.conf and no mention of fbcondecor in make.conf, splashutils updated to the newest version with the fbcondecor use flag enabled. Why it did so I don't know, but what I can also tell you is that on the x86 box with practically an identical make.conf, the same emerge --update --deep --newuse world updated splashutils without fbcondecor, which I'm guessing from these messages was your intended behaviour. Unfortunately, without that use flag enabled, although silent splash worked, verbose did not and when I hit f2 to switch to verbose during boot, I had a plain text screen. As I'm guessing many current users are probably using the gentoo livecd 2007 splash theme (as I am), it would seem to me that enabling the flag by default would be simpler. Your instructions for uvesafb do not mention needing to insert fbcondecor into make.conf in order for fbsplash to work. However, I have just looked at http://fbsplash.berlios.de/wiki/doku.php?id=docs:distros:gentoo which does mention inserting that use flag. It's your package and a great one at that, I love it and its one of the biggest reasons I use gentoo but I think for simplicity for new users who may not understand it all so well, either enable the flag by default or add an explanation in the instructions at http://dev.gentoo.org/~spock/projects/uvesafb/ .
(In reply to comment #5) > accept keywords in my make.conf and no mention of fbcondecor in make.conf, > splashutils updated to the newest version with the fbcondecor use flag enabled. > Why it did so I don't know, but what I can also tell you is that on the x86 And this is precisely what I would like to get explained first, before discussing the whole 'make fbcondecor enabled by default' thing :) So, if you run `emerge -pv splashutils` on the amd64 box, without fbcondecor enabled in make.conf, does the USE flag show up as enabled in the emerge output?
When running that here is what I get Calculating dependencies... done! [ebuild R ] media-gfx/splashutils-1.5.3.2 USE="gpm mng png truetype -fbcondecor* -hardened" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB Only thing is , when I originally emerged it, here is what my make.conf looked like # These settings were set by the catalyst build script that automatically built this stage # Please consult /etc/make.conf.example for a more detailed example CFLAGS="-march=native -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CXXFLAGS="${CFLAGS}" USE="3dnow 3dnowtext a52 aac aalib accessibility acpi aiglx alsa amarok amd64 apm arts artworkextra asf audiofile automount avahi avi bash-completion berkdb -bindist bitmap-fonts bittorrent branding bzip2 cairo calendar cann cdparanoia cdr cli cpudetection crypt cups curl dbus deprecated deprecated devil dga directfb discouraged dlloader doc dri dts dv dvb dvd dvdr dvdread eds effects elibc_glibc elisp emacs emerald emboss encode esd evo examples exif ext-man ext-rtf ext-tex extraicons fam fat fax fbcon fbsplash ffmpeg firefox flac flash foomaticdb fortran freetype fuse gcj gb gd gdphoto2 gdbm gedit gif gimp gimpprint glitz gnome gnutls gphoto2 gpm gstreamer gtk gtkhtml gtk2 hal hddtemp hfs howl html idn ieee1394 imagemagick imlib inkjar input_devices_evdev input_devices_keyboard input_devices_mouse ipv6 isdnlog jack java jfs joystick jpeg kde kdehiddenvisibility kerberos kernel_linux lcms ldap libcaca libao libg++ lirc lm_sensors logrotate mad mail mikmod mime mjpeg mmx mmxext mng mono mozbranding mozcalendar mozilla mplayer mp3 mpeg multilib mysql nas nautilus ncurses networking new-login newspr nforce2 nls nptl nptlonly nsplugin ntfs nvidia odbc offensive ogg opengl oss pam parport pcre pdf pdflib perl pmu png postgres ppds pppd python qt3 qt3support qt4 quicktime rar rdesktop readline real reflection regex reiser4 reiserfs S3TC samba scanner sdl seamonkey session skins slp smp sndfile snmp sound sounds speex spell spl spreadsheet sqlite sse sse2 ssl startup-notification streams subversion swat svg svga symlink sysfs syslog tcltk tcpd tetex theora thesaurus threads thunderbird tidy tiff timidity tk truetype truetype-fonts type1 type1-fonts udev unicode usb userland_GNU utempter utils v4l vcd vdr voice vorbis vram weather win32codecs wmf wordperfect X xattr xcb xcomposite xforms xfs xine xml xorg xpm xprint xscreensaver xvid xv zeroconf zlib" FEATURES="parallel-fetch fixpackages buildpkg" PORTDIR="/usr/portage" PORTAGE_ELOG_CLASSES="warn error log info qa" PORTAGE_ELOG_SYSTEM="save" PORTDIR_OVERLAY="/usr/local/portage/miscellaneous" AUTOCLEAN="yes" NOCOLOR="true" ACCEPT_KEYWORDS="~amd64" PORTAGE_NICENESS="19" MAKEOPTS="-j3" Nowhere in my use flags did it show fbcondecor, yet when I checked use flag status in kuroo, it showed it as emerged with fbcondecor. Very strange. I'm not sure why that happened with my system, it may have been a fluke but if the use flag isn't enabled by default and you feel its best left that way, it may be a good idea to add something here http://dev.gentoo.org/~spock/projects/uvesafb/ so that people who are using the new system know to emerge splashutils with the new use flag fbcondecor.
(In reply to comment #7) > I'm not sure why that happened with my system, it may have been a fluke but if > the use flag isn't enabled by default and you feel its best left that way, it I don't like the idea of a fluke very much, but since there seems to be no better explanation at this point, let's assume that it's indeed what it was. > may be a good idea to add something here > http://dev.gentoo.org/~spock/projects/uvesafb/ > so that people who are using the new system know to emerge splashutils with > the new use flag fbcondecor. uvesafb has nothing to do with fbsplash or fbcondecor, so I can't add the info there. I did however add an informational message to the splashutils ebuild -- it will be displayed to users upgrading from pre-1.5.3 versions, where the fbcondecor USE flag wasn't available.
That will work.
