public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Interactive emerge
Date: Mon, 3 Oct 2005 13:23:13 -0500	[thread overview]
Message-ID: <20051003182312.GA18244@nightcrawler.wit.org> (raw)
In-Reply-To: <43416CB9.7010600@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]

On Mon, Oct 03, 2005 at 07:39:05PM +0200, Jan Kundr?t wrote:
> Ciaran McCreesh wrote:
> > On Mon, 3 Oct 2005 23:15:37 +0900 Georgi Georgiev <chutz@gg3.net> wrote:
> > | Does it seem like it is time for RESTRICT=interactive. Such ebuilds
> > | would refuse to emerge if stdout is not a tty. If only there was
> > | use-flag based RESTRICT...
> > 
> > No, because then that would encourage even more people to abuse the
> > system and write incorrect ebuilds.
> 
> IMHO this could be enforced by some policy ("don't use
> RESTRICT=interactive unless you really need it and some_group has given
> you the ok")...

Ebuilds are non-interactive compile/install... that's the design, and 
intention of them.

I don't like opening the possibility for people to use it, mainly due 
to the fact
A) give me an instance when it's required for compile
B) interactive build scripts are idiotic (writing expect scripts for a 
tinderbox setup is proof enough of this)
C) 15 hour upgrade/build, hanging an hour into it is going to be an 
ass biter.

Yes, we can slap some warning into the UI tools for C, but people will 
still miss it on occasion, and it'll piss them off something fierce 
(just the same as a single failure in building results in emerge 
stopping).

It's a bad idea from where I sit.
~harring

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-10-03 20:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-02 17:21 [gentoo-dev] Interactive emerge Dan Meltzer
2005-10-02 17:41 ` Ciaran McCreesh
2005-10-02 17:50   ` Fernando J. Pereda
2005-10-02 17:57     ` Dan Meltzer
2005-10-02 18:01     ` Maurice van der Pot
2005-10-02 18:13       ` Fernando J. Pereda
2005-10-02 18:34         ` Re[2]: " Jakub Moc
2005-10-02 18:02     ` Ciaran McCreesh
2005-10-02 18:14       ` Fernando J. Pereda
2005-10-03 12:56 ` Chris Gianelloni
2005-10-03 14:15   ` Georgi Georgiev
2005-10-03 16:51     ` Ciaran McCreesh
2005-10-03 17:39       ` Jan Kundrát
2005-10-03 18:22         ` Patrick Lauer
2005-10-03 18:23         ` Brian Harring [this message]
2005-10-03 19:15           ` Chris Gianelloni
2005-10-03 19:29           ` Jan Kundrát
2005-10-03 19:12       ` Chris Gianelloni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051003182312.GA18244@nightcrawler.wit.org \
    --to=ferringb@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox