From: Thilo Bangert <thilo.bangert@gmx.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] User question during ebuild
Date: Thu, 14 Mar 2002 20:43:58 +0100 [thread overview]
Message-ID: <20020314201456.F3C522005FF7@chiba.3jane.net> (raw)
In-Reply-To: <001201c1cb6d$8d670fa0$4b00a8c0@metrony.com>
Hi,
On Thursday, 14. March 2002 16:33, you wrote:
> I've been playing around with Gentoo on and off since rc3 and I
> have a need for it now. I'm building a appliance style database
> server for a client and I want to use ebuilds to install and
> maintain my custom application as well as some patched utilities.
> During the install I'd like to ask the user some questions and
> take action based on the answer.
>
this is a dificult part - i feel. usually ebuilds are just ebuilds -
ie. the install software, they don't configure something.
this is however in a few cases done anyway (the qmail ebuild comes to
my mind - which pretty much sets up the whole thing) - but even though
the ebuild does configuration, it does not ask the user any questions.
IMHO ebuilds should not ask questions but run non-interactivly.
when gontran and me rebuild the djbdns ebuild, we choose to write some
setup scripts which then ask the user all the questions needed to get
one going.
(BTW. the new djbdns ebuild is not in portage yet - checkout
http://fizzelpark.com/portage/ )
this is very much MHO!
> Is there a framework for this type of activity?
well, there is bash :-)
>
> Thanks,
> -Aaron Held
--
regards
Thilo
next prev parent reply other threads:[~2002-03-14 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 15:33 [gentoo-dev] User question during ebuild Aaron Held
2002-03-14 19:43 ` Thilo Bangert [this message]
2002-03-14 20:27 ` Grant Goodyear
2002-03-14 21:11 ` Thilo Bangert
2002-03-14 22:01 ` Thilo Bangert
2002-03-15 3:07 ` Aaron Held
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=20020314201456.F3C522005FF7@chiba.3jane.net \
--to=thilo.bangert@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