1 |
In the process of creating a build server (a server which is capable of |
2 |
building all the packages in the portage tree to test if a given profile |
3 |
is broken, and maybe providing binary packages for people who desire |
4 |
them) I've found it was required to have portage to be able to log the |
5 |
[per package] ebuild output into a file (more likely in the /var/db/pkg/ |
6 |
tree), so that it could be analyzed later. In fact, this behavior is |
7 |
desirable generically, since it's sometimes useful to understand what |
8 |
happened in the building process of a given package. Is this |
9 |
functionality being planned for portage? Do you see any drawbacks to |
10 |
include it in the mainstream code? |