When I try to update from gcc 3.2.1-r0 to -r6, I see this message: Calculating dependencies ...done! >>> emerge (1 of 1) sys-devel/gcc-3.2.1-r6 to / >>> md5 ;-) gcc-3.2.1.tar.bz2 >>> md5 ;-) gcc-3.2.1-branch-update-20021208.patch.bz2 >>> md5 ;-) gcc-3.2.1-manpages.tar.bz2 * This is a very alpha ebuild and changes in here * are not yet set in stone! Please do NOT merge * this if you are not a developer! >>> Unpacking source... >>> Unpacking gcc-3.2.1.tar.bz2 As I see it, if the ebuild really *is* alpha, shouldn't it be masked? Or is this message in there by accident? Can I safely upgrade to -r6?
Well, if you have '~x86' in accepted keywords, I guess you do accept the fact that you may merge flaky stuff ? On another note, we had gcc-3.2-r5, gcc-3.2.1-r5 and now gcc-3.2.1-r6 and also gcc-2.95.3-r8 that all use the layout that -r6 uses, and so far its been fine for a lot of people. Actually, I think I have most if not all problems sorted out with -r6. Seemant: you are more up to terms with public relations ... the -r6 ebuild im guessing is fine (except for the 'hey, where did my /usr/bin/gcc go?' type of thing, which a source /etc/profile fixes) for most people, or was there complaints ?
Az: In fact, people seem to like this scheme a lot. Certainly Arun Thomas (sindian) is now fired up for cross-compiling for the ARM port (unofficially). Once everyone gets through those initial questions about "where did my /usr/bin/gcc go?" and the sourcing of /etc/profile, everything seems to work well. Is it possible, btw, to make the `source /etc/profile` step automatic?
Not as far as I know. For portage, this switch is transparent, but if you run gcc in console just after merge, it will fail. I dont know of a way to update the parent shell's environment from a child shell/process, in fact, I am 99% sure it cannot be done with bash/whatnot as they are now ... if anybody can correct me on this, Ill appreciate.
Message is removed.
