public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Robert Paskowitz <rpaskowitz@confucius.ca>
To: gentoo-catalyst@robin.gentoo.org
Subject: Re: [gentoo-catalyst] Patch for  targets/livecd-stage1/livecd-stage1-chroot.sh
Date: Wed, 26 Jan 2005 19:57:53 -0500	[thread overview]
Message-ID: <1106787473.3156.12.camel@localhost> (raw)
In-Reply-To: <1106772018.9470.115.camel@cgianelloni.nuvox.net>

> >  My understanding of portage_confdir is that a directory on the build
> > system is copied into the chroot as [chroot]/etc/portage. Changing the
> > USE_ORDER occurs within the chroot so that per-package flags are
> > respected. The actual location of the portage_confdir should have no
> > bearing on this. Also, a quick grep through the source shows that this
> > should be changed in 6 locations. If it's fine to make this change, I'll
> > create the patch.
> 
> Awesome.  Create a patch, file a bug, and I'll add it.
> 

I see you beat me to it on this one.

> > 2) Changes the behavior of 'verbose' mode, so that instead of a 15
second
> > delay, the user is prompted for input. I just realized this may not be
> > desired, as it would ruin automated builds, but for someone that wants to
> > see the package list, 15 seconds is generally not enough. Perhaps this
> > could be controled by different levels of verbosity, or another options?
> 
> I really would prefer to leave this alone for now.  I'll think about
> finding another solution.  I'm always welcome to ideas, but anything
> that breaks automatic builds is an absolute no.


How about something like the following:

echo "Press any key within 15 seconds to pause the build..."
read -s -t 15 -n 1 PAUSE
if [ -n "$PAUSE" ]; then
        echo "Press any key to continue..."
        read -s -n 1
fi

You still get the automated ability with the 15 second timeout, but someone that actually wants to stop and read can 'pause' the progress, then get it going again.

Robert

--
gentoo-catalyst@gentoo.org mailing list


  reply	other threads:[~2005-01-27  0:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-26 18:40 [gentoo-catalyst] Patch for targets/livecd-stage1/livecd-stage1-chroot.sh Robert Paskowitz
2005-01-26 19:23 ` Chris Gianelloni
2005-01-27  2:03   ` Robert Paskowitz
2005-01-27 12:32     ` Chris Gianelloni
2005-01-27 17:02       ` Robert Paskowitz
2005-01-27 18:06         ` Chris Gianelloni
2005-01-28  0:21         ` [gentoo-catalyst] LAMP-in-a-box Nathan de Vries
2005-01-28  2:32           ` William Kilian
2005-01-28  2:43           ` Robert Paskowitz
2005-01-28 14:52           ` Chris Gianelloni
2005-01-26 19:27 ` [gentoo-catalyst] Patch for targets/livecd-stage1/livecd-stage1-chroot.sh Chris Gianelloni
2005-01-26 19:48   ` Robert Paskowitz
2005-01-26 20:40     ` Chris Gianelloni
2005-01-27  0:57       ` Robert Paskowitz [this message]
2005-01-27 12:31         ` Chris Gianelloni
  -- strict thread matches above, loose matches on Subject: below --
2005-01-26 18:40 Robert Paskowitz

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=1106787473.3156.12.camel@localhost \
    --to=rpaskowitz@confucius.ca \
    --cc=gentoo-catalyst@gentoo.org \
    --cc=gentoo-catalyst@robin.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