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
-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
On Tue, 05 Aug 2008 23:26:22 -0700
Zac Medico [EMAIL PROTECTED] wrote:
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
Zac Medico wrote:
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.
No need for a convoluted and long
On Wed, 06 Aug 2008 00:37:26 -0600
Joe Peterson [EMAIL PROTECTED] wrote:
Zac Medico wrote:
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
On Wednesday 06 August 2008 07:37:26 Joe Peterson wrote:
You are trying to say it's a 'live' ebuild (i.e. it gets the sources from a
live source) - that's all. The locking issues are a technical detail
No, the locking issues are the whole point. There are other reasons to want
the package
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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
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
