Am I allowed to sync a portage tree while that (exported) tree is used by another system where a emerge is currently running ?
As long as portage itself isn't updated, the (remote) emerge shouldn't be affected, or ?

Last edited by toralf on Sat Jan 19, 2013 8:57 pm; edited 1 time in total

It's better to not sync while emerge is running. The reason being an ebuild could be deleted which is scheduled to be merged in the other running emerge. There are some other reasons too, but you get the gist of it _________________Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

Yes and no, the ebuild itself isn't actually read during dependency calculation, only when the actual build starts (well, under normal circumstances). Same for eclasses, patch files and some other stuff.

If you want non-blocking updating, there are other methods of sharing the tree. Namely using it as a local rsync mirror of which there are several forum threads, probably a wiki article or two about it. But then you have multiple copies of it locally. The alternative is to just pay attention to when you do the sync and when you have emerge running on systems. It could even be possible to wrap emerge with code that sets a lock that stops emerge from performing one action (sync) when the other is running (merge) and vice-versa._________________Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

they are seriously too conservative toralf, as soon as emerge is emerging something, all work is done on your PORTAGE_TMPDIR
so except the next emerge that may fail because the ebuild has been removed, it won't distrub your current emerge program and stop it, so yes, your openoffice build won't be stop even if you empty the tree, you just risk your emerge -u world been stopped.

Now it just depend how "buggy" it is for you to have emerge system|world been stopped.

It's been recommended that using sqaushfs for the tree (generate the image on the server) and sharing that image to be downloaded by the clients is much better. The sqaushfs images are an order of magnitude smaller than an expanded tree. And since each client has it's own copy, it will not encounter any problems like above. Then each client just RCU updates to the new image as it's available._________________Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...