Even though I've only installed vanilla-soruces-2.4.20, portage wants to install gentoo-sources. ;-) Someone could mess themselves up by doing an unattended 'emerge -u world'. This would result ing them losing all their custom kernel settings for the next time they go to build their kernels. ============================================================================== dragon root # emerge -pu world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild U ] sys-devel/gcc-3.2.1-r7 [3.2.1-r6] [ebuild U ] media-libs/libpng-1.2.5-r4 [1.2.5-r2] [ebuild U ] app-editors/xemacs-21.4.12 [21.4.11_rc1] [ebuild N ] sys-kernel/gentoo-sources-2.4.20-r1 [ebuild U ] sys-apps/lm_sensors-2.7.0 [2.6.5] [ebuild U ] dev-libs/libxml2-2.4.30 [2.4.28-r1] [ebuild N ] sys-apps/hotplug-20020826 [ebuild U ] net-print/cups-1.1.18-r2 [1.1.18-r1] [ebuild U ] media-libs/libsdl-1.2.5-r1 [1.2.5] [ebuild U ] media-libs/divx4linux-20020418-r2 [20020418-r1] [ebuild U ] media-video/mplayer-0.90_rc3 [0.90_rc2] [ebuild U ] dev-util/pkgconfig-0.15.0 [0.14.0] [ebuild U ] dev-libs/atk-1.2.2 [1.2.1] [ebuild U ] app-editors/vim-core-6.1-r4 [6.1-r3] [ebuild U ] app-editors/vim-6.1-r19 [6.1-r18] [ebuild U ] dev-util/netbeans-3.4.1 [3.4] [ebuild U ] app-emulation/wine-20030115 [20021125] [ebuild U ] sys-apps/diffutils-2.8.4-r2 [2.8.4-r1] [ebuild U ] sys-devel/autoconf-2.57 [2.54] [ebuild U ] sys-devel/automake-1.7.2 [1.6.3] [ebuild N ] media-libs/xvid-0.9.0 [ebuild N ] media-video/ffmpeg-0.4.6-r1 [ebuild U ] media-video/avifile-0.7.27.20030122 [0.7.25.20030114] [ebuild U ] sys-apps/gzip-1.3.3-r1 [1.3.3] [ebuild U ] app-admin/gentoolkit-0.1.17-r11 [0.1.17-r10] [ebuild U ] net-www/mozilla-1.2.1-r5 [1.2.1-r4] [ebuild U ] x11-themes/mosfet-liquid-widgets-0.9.6_pre2 [0.9.5-r1] [ebuild U ] net-libs/linc-1.0.1 [0.7.1] [ebuild U ] net-irc/xchat-1.8.11 [1.8.10-r1] =========================================================================== ragon root # ls -l /usr/src total 54 -rwxr-xr-x 1 root root 38609 Jan 15 19:00 fglrx_panel_sources.tgz -rwxr-xr-x 1 root root 9640 Jan 15 19:00 fglrx_sample_source.tgz lrwxrwxrwx 1 root root 12 Nov 29 16:23 linux -> linux-2.4.20 lrwxrwxrwx 1 root root 12 Dec 5 18:38 linux-2.4.19 -> linux-2.4.20 drwxr-xr-x 14 root root 1008 Jan 17 20:21 linux-2.4.20 drwxr-xr-x 7 root root 168 Nov 23 00:25 pc dragon root # emerge info Portage 2.0.46-r9 (default-x86-1.4, gcc-3.2.1, glibc-2.3.1-r3) ================================================================= System uname: 2.4.20 i686 AMD Athlon(TM) XP1900+ GENTOO_MIRRORS="http://www.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="" USE="x86 oss 3dnow apm avi crypt cups encode gif jpeg gnome libg++ mikmod mmx mpeg ncurses nls pdflib png qtmt quicktime spell truetype xml2 xmms xv zlib gtkhtml alsa gdbm berkdb slang readline arts bonobo svga tcltk java guile mysql X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gtk qt kde motif opengl mozilla cdr" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O3 -pipe" CXXFLAGS="-march=athlon-xp -O3 -pipe" ACCEPT_KEYWORDS="x86 ~x86" MAKEOPTS="-j1" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache" ===========================================================================
emerging the kernel would not mess up your custom settings at all ... if you have a /usr/src/linux ln then emerge wont touch it did you emerge vanilla-sources or did you d/l it yourself ?
I 'emerge vanilla-sources'. In fact, I've encountered this on another vanilla-sources machine as well. It's good to know that ones kernel settings won't be borked in that sistuation. My understanding was that you needed to save your .config file to some.other.name and then restore it. But I just realized that I got that confused with some other instuctions I have for restoring the kernel soruce to a pristing state and then recovering your personal kernel settings. ;P
that is because lm_sensors-2.7.0 needs to have a specific subset of kernel- sources in order to work, previous lm_sensors worked with all current kernel's i2c code... if you manually merge i2c-2.7.0 it will also satisfy that dependency... Not sure how this could be handled better. Aside from which, you can merge any number of kernel sources at the same time and it won't hurt anything...
I see, and what's more - I even understand. :-) Now that I do understand what's going on, I have no problem with this being closed. However, you may want to keep this open anyway. I suspect this will confuse many people with the whole "I'm (dazed &) confused. You guys must be doing something wrong (sic)." shtick. ;P I have no idea of the mechanics behind all this, but perhaps you might want to create another set of 'kernel sources' and call it "dependency-sources". The concept would be just to put those files needed to satisfy a dependency like for I2C-2.7.0. I can see were this could get messy under two circumstances. 1) What happens when two different packages require different versions of the same kernel files. Highly unlikely in my opinion - but mentioned for completeness. 2) What happens when someone already has the dependency met in the kernel sources they have? And then the kernel versions are changed. If you can create such a set of kernel sources, I think this would be much less confusing to most of us (dufus) users. ;-)
Yeah, this needs some more ponderings, maybe a virtual/i2c-version if portage supports that may be in order so that we can do provides and have a list... not sure.
Blah, this doesn't really need fixing, at some point a virtual/i2c might be a good idea, but for now, I'm leaving it out.
