public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: thomas weidner <yasea@gmx.net>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: something like debconf for gentoo?
Date: Sat, 16 Aug 2003 18:23:09 +0200	[thread overview]
Message-ID: <pan.2003.08.16.16.23.09.159552@gmx.net> (raw)
In-Reply-To: 1061017880.16765.19.camel@biproc

On Sat, 16 Aug 2003 09:11:21 +0200, Philippe Lafoucrière wrote:

> 
>> The problem is, emerge should be non-interactive, meaning I could walk
>> away for 12 hours and have it be done when I come back, not have some
>> silly gentooconf screen waiting on the second of 250 packages. That's
>> why USE flags are nice. Of course, if one could go through gentooconf
>> all at once before starting, that might work too.
> 
> Like debconf is only called when all packages are fetched, gentooconf
> should be called between fetching files and compiling.
> It's similar to the grouped log in emerge (display all messages in 1
> shot at the end of emerging).

that's a good idea,scan all packages first for gentooconf things,then do
the gentooconf stuff and then compile 250 packages non-interactively for
12h. (there aren't only useflags things to do with gentooconf)


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-08-16 16:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-15 13:19 [gentoo-dev] something like debconf for gentoo? thomas weidner
2003-08-16  3:29 ` Matt Thrailkill
2003-08-16  4:18   ` Jon Portnoy
2003-08-16  6:33     ` Philippe Lafoucrière
2003-08-16  6:46       ` Mike Frysinger
2003-08-16  6:44         ` donnie berkholz
2003-08-16  7:11           ` Philippe Lafoucrière
2003-08-16 16:23             ` thomas weidner [this message]
2003-08-16  9:26       ` Georgi Georgiev
2003-08-16 17:04         ` Fred Van Andel

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=pan.2003.08.16.16.23.09.159552@gmx.net \
    --to=yasea@gmx.net \
    --cc=gentoo-dev@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