-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ciaran McCreesh wrote: > On Tue, 05 Aug 2008 22:55:06 -0700 > Zac Medico <[EMAIL PROTECTED]> wrote: >> Would having the ebuild perform locking be unportable or introduce >> any undesirable complexity? Does it really need to be so >> fine-grained? > > It's not particularly tricky, and the lock code can be moved into an > eclass if necessary. And the gain is worth it -- scm fetches can be > slow, so parallelising fetches from different hosts will speed things > up quite a bit. > >> I don't see flock listed in the spec here [1]. > > If any platform doesn't have flock, there're various other ways of > doing locking using mkdir and either a fifo or just plain old sleep. >
To simplify things, how about if we just do a PROPERTIES=live-src-unpack for now, to indicate exclusive access to $DISTDIR during src_unpack? Thats a simple and portable baseline that will be quite useful even without anything finer grained. Zac -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkiZRA0ACgkQ/ejvha5XGaNZsACfVMIzQgQufKgbMrM6TyjKowN4 PQIAn1jTnV7omQaoezbU3cR4eS/hZrAU =I00K -----END PGP SIGNATURE-----
