After installing gentoo using the gentoo installer I noticed that the livecd flag has been previously set. It is evident when I use emerge --pretend --verbose for different ebuilds. I was brought to my attention when I had a problem with vim and showed my emerge --pretend --verbose output. I was then told that I had previously used the livecd USE flag, but I knew it couldn't have been possible since when I boot into my new gentoo system, I had no USE flags set. I had to manually set them myself and I wasn't aware of this USE flag. That's when I the person I spoke with stated that it was a GLI bug and that I should file it. I'm on a DELL Inspiron 1300 Intel Celeron M (using x86 version of Gentoo 2006.0) The GLI installer did quit with an error when installing extra packages. I read that the system is still bootable if the error occured here. I've since emerge sync'd and worry that a lot of installed packages may be broken because of this. If there's anymore information needed, I do not mind sharing it.
I assume you talked with ciaranm. Is 'livecd' in USE in /etc/make.conf, or does it just show as a flag that was enabled before but isn't now when you run 'emerge -pv vim'?
Its not in USE in the make.conf because I didn't know of it to even put it there. As I said I had no USE flags in the make.conf after I booted into the newly installed gentoo. I had to add them myself. And yes it shows that it was previously enabled when I did emerge -pv vim but isn't now.
This is expected behavior and is not a bug. The LiveCD has to be built with the livecd USE flag for things to be built properly. When you perform a networkless (GRP) installation of packages, they are installed as binaries using the same USE flags they were built with for the CD. This is a requirement for proper binary packages. The USE that is set is the default for the profile used to build the LiveCD itself, plus a few other required USE flags (livecd and bindist) for functionality and legal reasons. We have no intentions on changing this, as it would require a complete redesign of all of our installtion methods. When you eventually recompile your packages, they will be compiled with the USE that you have chosen, rather than the USE we chose. This is the nature of binary packages and how they are expected to work on Gentoo. Thanks for reporting this, but it is expected and wanted behavior.
