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 ebuild still doesn't have this value in it, portage will > *look* like it has hung itself out to dry. I have no idea if this is easy to > fix or not. If it is easy, then I still would like to propose that it gets > sent to the foreground when in background mode. What will portage's behavior > be when the user asks to be in background mode and there is an ebuild in the > depgraph that has PROPERTIES=interactive? If it bails out, then the problem > described above is moot (only if maintainers are diligent).
The build will also fail if the maintainer is not diligent enough to add proper packages to DEPEND; I don't necessarily see how it makes that much difference adding more things for them to do. If you can propose a means to figure out if an ebuild is stuck waiting on something or actually doing work then propose it; otherwise I think this is good enough. -alec > > -Jeremy > >
