Can ebuild commands be executed in parallel?

[fpemud]

I am writing a script for batch modification of ebuild files and generation of new Manifest files.
I'd like to know whether executing many (hundreds of) ebuild commands in parallel would pose issues. I will do this job unattended & periodicly, robustness is important.

Specifically:
1. Does ebuild rely on shared resources that could lead to conflicts during parallel execution? (two packages may download same file to distfiles directory?)
2. Does ebuild command have enough locking mechanisms?

[szatox]

You should be good unless you really let loose to the point of running out of resources. While not theoretically impossible, doing it with manifests would be quite an achievement.
There's nothing to lock unless you're actually merging those packages. Emerge resolves dependencies and tries to keep your system usable at all times, that's why it needs to calculate a plan first.
_________________
Make Computing Fun Again

[NeddySeagoon]

fpemud,

Take care you don't waste resources building the same package multiple times.
That happens, when you parellel build packages with a common dependency.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[Zucca]

If you're only doing source fetching and manifest creation, then do the fetching in series and after that you can do the manifest refreshing in parallel.
_________________
..: Zucca :..

[fpemud]

Thank you, guys!