[gentoo-portage-dev] Does 2.1 retain eclass info in binpkgs?

[Duncan]

I'm doing some testing of the latest eselect-compiler for eradicator,
involving merging and unmerging gcc.  He has made some recent changes to
toolchain.eclass that are supposed to help it work with eselect-compiler,
and that's what I'm trying to test.  Obviously, gcc is a rather huge
package to go thru the entire merge every time just to test a bit of the
post-merge compiler selection script, and AFAIK, while the ebuild is
stored with the binpkg, and both the ebuild and dependent classes are
stored in the merged package database, merging a binpkg still uses the
current in-tree eclasses.  That's what I'm hoping, anyway.  

Is that a true summation or does portage 2.1 now retain build-time eclasses
in the binpkg, rather than using those in the tree, when merging the
binpkg?

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-portage-dev@g.o mailing list