From: Jerry A! <jerry@thehutt.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: AW: [gentoo-dev] Selection for KDE base-packages
Date: Fri Aug 24 08:55:01 2001 [thread overview]
Message-ID: <20010824105534.A31045@gemini.thehutt.org> (raw)
In-Reply-To: <998651075.6677.6.camel@fry>; from hallski@gentoo.org on Fri, Aug 24, 2001 at 01:04:35PM +0200
On Fri, Aug 24, 2001 at 01:04:35PM +0200, Mikael Hallendal wrote:
: Den 24 Aug 2001 11:04:59 +0200 skrev Sebastian Werner:
: > The root makefile contains a variable TOPSUBDIRS which select the
: > subdirs to build and install.
: > We could patch this file to delete some entries in this variable.
: >
: > I mean that i don't want to use three editors for example. I need
: > only one editor in KDE: kate
: > So i wouldn't install kedit for example
:
: What about the people that _do_ want kedit and not kate?
: I would like some pre-build configuration stuff. With a question to the
: user, do you want to configure this package before building it? It would
: make the Portage tree more flexible than just using USE-variables. I'm
: not sure if this fits into the Portage system though.
:
: But in this case it would be something like:
:
: Do you want to configure KDE-base [y/N]: Y
: Which editor would you like: [Kate/kedit/all]: <enter>
: ...
: Installing KDE-base with the following programs:
: Editor: Kate
: ...
: Is this correct [Y/n]: <enter>
: Start installing..
:
: We could have some kind of timeout on the first question so that if you
: do an automatic build it wouldn't stop at the question if you are not at
: the computer.
:
: What do you think, drobbins?
I think that this goes against the current vision of the portage system.
Currently, a portage should build w/out *any* user interaction. There
are still some bugs to get worked out, but I think that's still where
we're heading. Keep in mind, I'm not speaking for Dan, just relating
things as I understand them.
That being said, I want to once again point out that the portage system
does allow one to have a /usr/portage/local directory. Have you thought
about configuring the ebuild to meet your specific needs and sticking it
in there?
--Jerry
name: Jerry Alexandratos || Open-Source software isn't a
phone: 703.599.6023 || matter of life or death...
email: jerry@thehutt.org || ...It's much more important
|| than that!
next prev parent reply other threads:[~2001-08-24 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-23 14:44 [gentoo-dev] Selection for KDE base-packages Sebastian Werner
2001-08-23 16:32 ` Dan Armak
2001-08-23 16:47 ` Mikael Hallendal
2001-08-24 1:47 ` Dan Armak
2001-08-24 3:05 ` AW: " Sebastian Werner
2001-08-24 4:11 ` Dan Armak
2001-08-24 5:06 ` Mikael Hallendal
2001-08-24 8:55 ` Jerry A! [this message]
2001-08-24 9:48 ` Mikael Hallendal
2001-08-28 23:31 ` Daniel Robbins
2001-08-24 8:33 ` Achim Gottinger
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=20010824105534.A31045@gemini.thehutt.org \
--to=jerry@thehutt.org \
--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