From: Sean Mitchell <SMitchell@phoenix-interactive.com>
To: gentoo-dev@cvs.gentoo.org
Subject: RE: [gentoo-dev] Suggestion: DONT_USE flags
Date: Wed Jul 18 11:41:01 2001 [thread overview]
Message-ID: <1DCB85BD45DED211B12D009027279E4F4767CB@murcury> (raw)
> I agree. I think interactive ebuilds are very powerful and important.
>
> The ebuilds would ask questions - what libraries to link with
> etc., and
> possibly configuration options could be added. The USE flags
> would become the
> system-wide default answers.
>
> In the meantime, if drobbins/achim/everyone else don't want
> to change emerge
> to suit (maybe not yet), we should at least decide on a standard
> question/ansewr format and perhaps add a simple handler
> function to emerge.
I haven't taken a really good look at emerge yet, but from what I've seen
this could actually be implemented in the src_compile() function of the
ebuild itself. It would mean a bit of redundant functionality in the ebuilds
themselves, but I think it could accomplish the purpose.
Sean
------------------------------------------------------------------------
Sean Mitchell Software Engineer
smitchell@phoenix-interactive.com Phoenix Interactive Design Inc
tel. 519-679-2913 x237 4th Floor, 137 Dundas St
fax. 519 679 6773 London, ON, Canada N6A 1E9
ICQ# 104246806
------------------------------------------------------------------------
next reply other threads:[~2001-07-18 17:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-18 11:41 Sean Mitchell [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-18 12:14 [gentoo-dev] Suggestion: DONT_USE flags Sean Mitchell
2001-07-18 11:39 Sean Mitchell
2001-07-18 7:34 Sean Mitchell
2001-07-18 10:54 ` Dan Armak
2001-07-18 5:29 Dan Armak
2001-07-18 11:13 ` Daniel Robbins
2001-07-18 11:20 ` Dan Armak
2001-07-18 11:53 ` Daniel Robbins
2001-07-18 12:06 ` Dan Armak
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=1DCB85BD45DED211B12D009027279E4F4767CB@murcury \
--to=smitchell@phoenix-interactive.com \
--cc=gentoo-dev@cvs.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