Zac Medico wrote:
Like Alec said, I don't think this is a difficult thing to get right
and even if the maintainer doesn't get it right initially then it's
not something that's very difficult to spot and fix. More elusive
bugs certainly do exist. That said, I still would like to make use
of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello again,
Please consider a new PROPERTIES=interactive setting that allows an
ebuild to indicate that it uses stdin and stdout for user
interaction sometime during the pkg_setup and/or src_unpack phases
(similar to GLEP 52 [1]). This will be
On Wed, Aug 6, 2008 at 2:22 AM, Zac Medico [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello again,
Please consider a new PROPERTIES=interactive setting that allows an
ebuild to indicate that it uses stdin and stdout for user
interaction sometime during the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alec Warner wrote:
Just to be clear; PROPERTIES is a space separated list of items correct?
I was thinking that it might support the same syntax as RESTRICT,
which includes support for USE conditionals.
Zac
-BEGIN PGP SIGNATURE-
Version:
Please consider a new PROPERTIES=interactive setting that allows an
ebuild to indicate that it uses stdin and stdout for user
I don't think anyone will disagree with this one. The one problem that I
see is that if the ebuild still doesn't have this value in it, portage
will *look* like it has
On Wed, Aug 6, 2008 at 9:27 PM, Jeremy Olexa [EMAIL PROTECTED] wrote:
Please consider a new PROPERTIES=interactive setting that allows an
ebuild to indicate that it uses stdin and stdout for user
I don't think anyone will disagree with this one. The one problem that I see
is that if the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Olexa wrote:
Please consider a new PROPERTIES=interactive setting that allows an
ebuild to indicate that it uses stdin and stdout for user
I don't think anyone will disagree with this one. The one problem that I
see is that if the ebuild
