From: "MooktaKiNG" <Mooktakim@hotmail.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] A nice idea to improve portage
Date: Tue, 10 Jun 2003 22:56:07 +0100 (BST) [thread overview]
Message-ID: <1206.10.0.0.1.1055282167.squirrel@mooktaking.homeip.net> (raw)
In-Reply-To: <1055268327.5107.578.camel@isengard.aravir.net>
But i usually start an emerge and then do && halt
This shutsdown gentoo after the emerge.
Its still the same problem.
But why can't we have both?
A readme should not me too hard. The person who makes the actual
ebuild just types a small README to explain stuff. Thats all.
>> I know i know. there are some text at the end of the emerge that
>> says what you should do.
>>
>> But when your doind multiple emerge's one after the other and you
>> leave gentoo todo its thing. You don't see the text.
>>
>> So if there was a nice README file that explain the 'extra'
>> setting
>> needed on each dir in portage then it would make things a LOT
>> easier
>> and would be very helpful.
>
> Honestly, I think I'd much prefer if portage just queued all of
> those
> messages and displayed them at the end of the emerge. If that
> information was in a README, you'd have to go, find, and read the
> README
> for every package and dependency that you install. That's a lot of
> work.
> Since portage is supposed to be non-interactive, it shouldn't assume
> that you're gonna stick around watching the terminal while it does
> its
> thing. ;)
>
> - John
>
> --
>
> Love justice; desire mercy.
>
>
> --
> gentoo-dev@gentoo.org mailing list
>
>
-------------------------------------------------
Please wait while you are redirected to my signature......
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-06-10 20:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 14:25 [gentoo-dev] ebuild question MAL
2003-06-10 15:40 ` [gentoo-dev] A nice idea to improve portage MooktaKiNG
2003-06-10 16:07 ` Matthew Kennedy
2003-06-10 18:05 ` John Robinson
2003-06-10 20:20 ` Philippe Lafoucrière
2003-06-11 3:18 ` Luke Graham
2003-06-11 5:10 ` Bill Kenworthy
2003-06-10 21:56 ` MooktaKiNG [this message]
2003-06-10 21:42 ` Zach Forrest
2003-06-10 23:26 ` Kumba
2003-06-11 11:52 ` [gentoo-dev] Readme files for portage (was: A nice idea to improve portage) Svyatogor
2003-06-11 10:37 ` MooktaKiNG
2003-06-11 10:10 ` Michael Cummings
2003-06-11 10:44 ` Paul de Vrieze
2003-06-11 13:24 ` [gentoo-dev] " D. Tuinstra
2003-06-11 15:47 ` oford
2003-06-11 17:06 ` [gentoo-dev] " MooktaKiNG
2003-06-12 11:34 ` [gentoo-dev] ebuild question Amiel Martin
-- strict thread matches above, loose matches on Subject: below --
2003-06-10 18:16 [gentoo-dev] A nice idea to improve portage Balaji Srinivasan
2003-06-10 18:36 ` Marius Mauch
2003-06-10 18:46 ` John Robinson
2003-06-10 20:02 ` Todd Berman
[not found] ` <1055271494.8194.8.camel@devweb>
2003-06-10 20:11 ` John Robinson
2003-06-10 20:15 Balaji Srinivasan
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=1206.10.0.0.1.1055282167.squirrel@mooktaking.homeip.net \
--to=mooktakim@hotmail.com \
--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