-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Donnie Berkholz wrote: > On 01:44 Tue 09 Dec , Federico Ferri wrote: >> today I hit this annoyance, because my laptop hung in the middle >> of an 'emerge -e @world' (checking that my world set compiles >> with gcc-4.3... stopped at ~ 300 of 700 :S ) >> >> I was looking for an entry in /var/db/pkg/<cat/pkg>/ that could >> have told me the compiler used to build the package, but couldn't >> find any. indeed it would be a fairly useful feature to have, >> both for testing purposes, and for user's everyday maintenance. >> >> please criticize this with anything constructive you can think >> of. > > As I mentioned on IRC, I think this isn't a very general use case > (given the existence of --resume, --keep-going, etc.) so code to > accomplish it the point was not resuming my emerge because the laptop hung. was more like: tracking which compiler built which package or vice-versa > would be better put into a custom portage bashrc than into portage > proper. yes, that makes sense. it could be an external tool, like revdep-rebuild is, which queries compiler by pkg, and eventually rebuilds packages (not) matching a certain compiler.
but to accomplish this, an information about the compiler (in the pkg record) should be there. something like /var/db/pkg/<cat>/<pkg>/COMPILER - -- Federico Ferri -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkk+8qQACgkQV/B5axfzrPs9BwCbBmbU3HVY0i6bqljlx3yZqICk nT8AoJpgTbcNc/UOirCrPRw3zTOlxI5G =uWSJ -----END PGP SIGNATURE-----