With some inside knowledge of the system. I know that the host packages.g.o is on has the following characteristics that differ from the rest of the infra hosts:
- emerge --sync every 6 hours for qa checks
- has a full portage tree in PORTDIR vs the smaller infra tree on the rest of the hosts.
Ergo, I suggest that we cut down on some IO activity and leverage the system PORTDIR for packages.g.o. It goes without saying that the system PORTDIR will need to be updated more often.
+1 on at least using the same PORTDIR for QA+gpackages.
Not sure if we should having a full PORTDIR for system use however.
(In reply to comment #1)
> Not sure if we should having a full PORTDIR for system use however.
It might be rude to ask third party script writers to support a non-standard PORTDIR. Anyway, I don't see a problem with it - what's the concern?
Any tool wanting to use the contents of PORTDIR should be willing to read the variable. Everything I know is capable of doing so.
Just more that we get better subjective results when all of our boxes use the same PORTDIR contents for building.