-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ciaran McCreesh wrote: > On Sun, 03 Aug 2008 18:52:43 -0700 > Zac Medico <[EMAIL PROTECTED]> wrote: >> As a substitute for the previously discussed RESTRICT=live value[1], >> I'd now like you to consider an equivalent PROPERTIES=live-sources >> setting. By specifying PROPERTIES=live-sources, an ebuild will be >> able to indicate that it uses src_unpack() to download sources from >> some type of live repository such as cvs, darcs, git, mercurial, or >> svn. > > You're using a single value to mean: > > * include me in some 'live-sources' set > * I need some kind of locking in src_unpack > > At the very least, the two should be separate attributes. But the > locking probably shouldn't be an attribute at all -- the 'flock' shell > utility can be used instead to get much more fine-grained locking. >
Would having the ebuild perform locking be unportable or introduce any undesirable complexity? Does it really need to be so fine-grained? I don't see flock listed in the spec here [1]. Zac [1] http://www.opengroup.org/onlinepubs/009695399/utilities/contents.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkiZPLkACgkQ/ejvha5XGaML7ACg9Fuam5ZmwRst/kIsBvmJG8H7 vbEAoIOrAZCvijO5yN3PxbufXLQyQB03 =kPf6 -----END PGP SIGNATURE-----
