public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marius Mauch <genone@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Interaction in ebuilds - bad idea?
Date: Fri, 30 Apr 2004 23:53:20 +0200	[thread overview]
Message-ID: <20040430235320.27cc39e0@sven.genone.homeip.net> (raw)
In-Reply-To: <200404302239.55447.stuart@gentoo.org>

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

On 04/30/04  Stuart Herbert wrote:

> On Friday 30 April 2004 22:06, Ryan Phillips wrote:
> > I think this is a really good idea.  The ebuild config mechanism is
> > not all that smart.  
> 
> Let's try and make it smarter.
> 
> For example, if we absolutely *have* to ask the user for some
> information for an ebuild - if there's no way to script it (and I
> think there is) - let's make Portage ask all the questions *before*
> downloading and compiling anything.  It makes sense to ask all the
> questions up-front, so that the user doesn't constantly have to check
> his 'emerge -u world' to see if it has stopped to ask a question.
> 
> Imagine running, for an example, 'emerge -u world'.  Once Portage has 
> calculated the dependencies, it could call a function (let's call it 
> pkg_askuser) in each ebuild to gather further information. 
> pkg_askuser would need some library functions to call, so that we can
> standardise the user's experience.  Portage would have to cache the
> information gathered by pkg_askuser, and then it could continue with
> running each ebuild in turn exactly as it currently does.  Each ebuild
> would have access to the cache (how doesn't matter yet), so that it
> can use the right database server, the right user and password, or
> whatever that information needs to be.

I don't like that idea, portage shouldn't be interactive by default. Use
pkg_setup() and tell the user to set the required values via the
environment or with a tool, let's call it gentoo-db-config for now.
That's the standard way to do such things (java-config, gcc-config) and
I don't see why databases should be an exception.

Marius

-- 
Public Key at http://www.genone.de/info/gpg-key.pub

In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.

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

  reply	other threads:[~2004-04-30 21:53 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29 21:04 [gentoo-dev] Interaction in ebuilds - bad idea? Ajai Khattri
2004-04-29 21:01 ` Eldad Zack
2004-04-29 21:32   ` Ajai Khattri
2004-04-29 21:36     ` Nick Rout
2004-04-29 21:41       ` Tom Wesley
2004-04-29 23:07         ` Andy Arbon
2004-04-30 23:03       ` Aiko Barz
2004-05-01 11:03   ` Chris Bainbridge
2004-04-29 21:20 ` Stuart Herbert
2004-04-30 21:06   ` [gentoo-dev] " Ryan Phillips
2004-04-30 21:39     ` Stuart Herbert
2004-04-30 21:53       ` Marius Mauch [this message]
2004-04-30 22:28         ` Stuart Herbert
2004-04-30 22:35           ` Brandon Hale
2004-05-01 15:50             ` Wazow
2004-04-30 22:51           ` Grant Goodyear
     [not found]             ` <200405010041.00301.stuart@gentoo.org>
2004-05-01  0:13               ` Grant Goodyear
2004-05-01  0:33                 ` Stuart Herbert
2004-05-01  3:36                   ` Jeremy Maitin-Shepard
2004-05-01 13:05                     ` Jason Stubbs
2004-05-01 19:10                       ` Chris Gianelloni
2004-05-01 16:03                     ` Wazow
2004-05-01 16:38                       ` Stuart Herbert
2004-05-01 15:56                   ` Paul de Vrieze
2004-05-01 19:52                     ` Jeremy Maitin-Shepard
2004-05-01 20:12                       ` Marius Mauch
2004-05-01 21:03                       ` Paul de Vrieze
2004-05-01  0:05           ` Marius Mauch
2004-05-01 18:26       ` 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=20040430235320.27cc39e0@sven.genone.homeip.net \
    --to=genone@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