I want portage to emerge complete directorys. Suppose on Computer A, I've emerged all packages with -b. Now I copy that directory on a CD-rom and want my Laptop B to have the same Software. It would be goot If I coult type: emerge /mnt/cdrom/package-dir/ for packages or emerge /mnt/cdrom/source-archive-dir for source archives. and then portage would analyze the depencies and what to emerge first and if emerge is possible and try to emerge most of the packages. This would improve network installation of gentoo.
for this functionality, it would also be glad if portage would have a processor, and useflag-checking. It would cost a little to store the processor and the useflags the package was compiled with in the bz2 file and check them before emerge, just to assure that Packages that run only on a P4 dont get installed on a 386 for example
umm, you could simply do: cd /mnt/cdrom/package-dir/ emerge *
OK. Then i consider this bug as resolved. Only this item with the processor flags would be interesting.
portage does store CFLAGS and USE settings in the binary packages it makes ... i can see where you're going with the CFLAGS thing ... that would take some parsing on the portage side of things ... but i'm not so sure about the USE check you'd like to see
with the useflags: portage can shorly check the useflags. A package compiled with scanner installing where no scanner is available (-scanner useflag) makes no sense. (In my opinion it would also be good if I have an option io portage which can detect what packages must be recompiled when a Useflag is changed. That means: when I set scanner, and run portage with an option it tells me that kde-graphics must be recompiled. Portage puts a "Sucsess" file with no content at the end, when it is compiling. There it could also store the use parameters and cflags it has compiled the package with. When it compresses this information to bz2, not sufficient space will be lost) Such a mechanism could also be used when checking binary packages
*** Bug 34064 has been marked as a duplicate of this bug. ***
Rebuild on use change is a feature to be implemented with the dep rewrite. Closing this -- too much extraneous info in this bug.