| 1 |
On Tue, 05 Aug 2008 22:55:06 -0700 |
| 2 |
Zac Medico <zmedico@g.o> wrote: |
| 3 |
> Would having the ebuild perform locking be unportable or introduce |
| 4 |
> any undesirable complexity? Does it really need to be so |
| 5 |
> fine-grained? |
| 6 |
|
| 7 |
It's not particularly tricky, and the lock code can be moved into an |
| 8 |
eclass if necessary. And the gain is worth it -- scm fetches can be |
| 9 |
slow, so parallelising fetches from different hosts will speed things |
| 10 |
up quite a bit. |
| 11 |
|
| 12 |
> I don't see flock listed in the spec here [1]. |
| 13 |
|
| 14 |
If any platform doesn't have flock, there're various other ways of |
| 15 |
doing locking using mkdir and either a fifo or just plain old sleep. |
| 16 |
|
| 17 |
-- |
| 18 |
Ciaran McCreesh |
Archives