* [gentoo-dev] A nice idea to improve portage
2003-06-10 14:25 [gentoo-dev] ebuild question MAL
@ 2003-06-10 15:40 ` MooktaKiNG
2003-06-10 16:07 ` Matthew Kennedy
2003-06-10 18:05 ` John Robinson
0 siblings, 2 replies; 15+ messages in thread
From: MooktaKiNG @ 2003-06-10 15:40 UTC (permalink / raw
To: gentoo-dev
I think it would be better if portage included a README file for
each ebuild.
This i belive is very important becuase gentoo is a bit different
from a normal linux.
Like when installing a mod_php you run the command:
ebuild .../mod_php config
after installtion.
See when i installed this first i had know idea.
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.
If this already exists please ignore this email.
-------------------------------------------------
Please wait while you are redirected to my signature......
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [gentoo-dev] A nice idea to improve portage
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
1 sibling, 0 replies; 15+ messages in thread
From: Matthew Kennedy @ 2003-06-10 16:07 UTC (permalink / raw
To: gentoo-dev
"MooktaKiNG" <Mooktakim@hotmail.com> writes:
> I think it would be better if portage included a README file for
> each ebuild.
>
I think this is a good idea. Many ebuilds already include a
REAME.Gentoo which contains extra information. Its possible that
this is not used consistently though.
Matt
--
Matthew Kennedy
Gentoo Linux Developer
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [gentoo-dev] A nice idea to improve portage
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-10 21:56 ` MooktaKiNG
1 sibling, 2 replies; 15+ messages in thread
From: John Robinson @ 2003-06-10 18:05 UTC (permalink / raw
To: gentoo-dev
> 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
^ permalink raw reply [flat|nested] 15+ messages in thread
* RE: [gentoo-dev] A nice idea to improve portage
@ 2003-06-10 18:16 Balaji Srinivasan
2003-06-10 18:36 ` Marius Mauch
2003-06-10 18:46 ` John Robinson
0 siblings, 2 replies; 15+ messages in thread
From: Balaji Srinivasan @ 2003-06-10 18:16 UTC (permalink / raw
To: 'strider@aravir.net', gentoo-dev
A better idea would be if portage wrote those messages to a file and we
could view it when we wanted. ie. We could have a showEbuildMessages or some
such program that showed all those messages and allowed you to ack each one.
I think this would be pretty useful as normally when i am fixing things i
dont have time to fix all of it in one shot...
Balaji
-----Original Message-----
From: John Robinson [mailto:strider@aravir.net]
Sent: Tuesday, June 10, 2003 11:05 AM
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] A nice idea to improve portage
> 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
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [gentoo-dev] A nice idea to improve portage
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
1 sibling, 0 replies; 15+ messages in thread
From: Marius Mauch @ 2003-06-10 18:36 UTC (permalink / raw
To: gentoo-dev
On Tue, 10 Jun 2003 11:16:18 -0700 Balaji Srinivasan wrote:
> A better idea would be if portage wrote those messages to a file and
> we could view it when we wanted. ie. We could have a
> showEbuildMessages or some such program that showed all those messages
> and allowed you to ack each one. I think this would be pretty useful
> as normally when i am fixing things i dont have time to fix all of it
> in one shot... Balaji
Seems good to me, as an addition let portage notify us when it has
written any messages during the current emerge (in big red letters ;)
Marius
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 15+ messages in thread
* RE: [gentoo-dev] A nice idea to improve portage
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>
1 sibling, 2 replies; 15+ messages in thread
From: John Robinson @ 2003-06-10 18:46 UTC (permalink / raw
To: gentoo-dev
On Tue, 2003-06-10 at 14:16, Balaji Srinivasan wrote:
> A better idea would be if portage wrote those messages to a file and we
> could view it when we wanted. ie. We could have a showEbuildMessages or some
> such program that showed all those messages and allowed you to ack each one.
> I think this would be pretty useful as normally when i am fixing things i
> dont have time to fix all of it in one shot...
I agree; that would be an excellent idea. I would, however, at least be
in favor of portage printing something in red at the end of an emerge
stating that the file had been updated and needed to be looked at;
better, if it would print the (newly added) contents of the file. Some
of the messages printed are about crucial things that need to be done,
often configuration changes; leaving them to be read only if one feels
like it might leave people thinking that the messages there don't apply
to them.
- John
--
Love justice; desire mercy.
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 15+ messages in thread
* RE: [gentoo-dev] A nice idea to improve portage
2003-06-10 18:46 ` John Robinson
@ 2003-06-10 20:02 ` Todd Berman
[not found] ` <1055271494.8194.8.camel@devweb>
1 sibling, 0 replies; 15+ messages in thread
From: Todd Berman @ 2003-06-10 20:02 UTC (permalink / raw
To: gentoo-dev
On Tue, 2003-06-10 at 14:46, John Robinson wrote:
> On Tue, 2003-06-10 at 14:16, Balaji Srinivasan wrote:
> > A better idea would be if portage wrote those messages to a file and
we
> > could view it when we wanted. ie. We could have a showEbuildMessages
or some
> > such program that showed all those messages and allowed you to ack
each one.
> > I think this would be pretty useful as normally when i am fixing
things i
> > dont have time to fix all of it in one shot...
>
> I agree; that would be an excellent idea. I would, however, at least
be
> in favor of portage printing something in red at the end of an emerge
> stating that the file had been updated and needed to be looked at;
> better, if it would print the (newly added) contents of the file. Some
> of the messages printed are about crucial things that need to be done,
> often configuration changes; leaving them to be read only if one feels
> like it might leave people thinking that the messages there don't
apply
> to them.
>
> - John
Just a quick note. I agree completely that portage must somehow output
this information after a massive emerge, or store it somewhere, however,
I question the sanity of yet another small utility. We already have
etc-update, env-update, modules-update and a host of other 'small'
applications. In my experience helping people on #gentoo, one of the
most common problems is the average new gentoo user's lack of awareness
of the existence of these small helper applications.
Integrating this with etc-update or another -update application seems
like a far better idea than just writing another script.
In fact, the idea of replacing all of said applications with ONE
gentoo-update seems like something that should be approached in the near
future. Even if gentoo-update is just a shell script that calls other
shell scripts.
--Todd
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 15+ messages in thread
* RE: [gentoo-dev] A nice idea to improve portage
[not found] ` <1055271494.8194.8.camel@devweb>
@ 2003-06-10 20:11 ` John Robinson
0 siblings, 0 replies; 15+ messages in thread
From: John Robinson @ 2003-06-10 20:11 UTC (permalink / raw
To: gentoo-dev
> Just a quick note. I agree completely that portage must somehow output
> this information after a massive emerge, or store it somewhere, however,
> I question the sanity of yet another small utility. We already have
> etc-update, env-update, modules-update and a host of other 'small'
> applications. In my experience helping people on #gentoo, one of the
> most common problems is the average new gentoo user's lack of awareness
> of the existence of these small helper applications.
I can't speak for anyone else, but I didn't mean to suggest an update
utility, and I didn't read anyone else's posts to mean that, either. I
can see how that would be a logical next step from what was said, but I
had rather the idea that Balaji was envisioning something more like a
log, which the user could check manually if he or she felt like it.
Now that you mention it, Gentoo tends to deal with such logs by way of
update applications, but in my mind the most that's needed would be a
file listing the "run ebuild config" sorts of messages generated by an
emerge. The next time an emerge was run, this file would be replaced.
> Integrating this with etc-update or another -update application seems
> like a far better idea than just writing another script.
> In fact, the idea of replacing all of said applications with ONE
> gentoo-update seems like something that should be approached in the near
> future. Even if gentoo-update is just a shell script that calls other
> shell scripts.
I completely agree. I'd love to see that.
- John
--
Love justice; desire mercy.
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 15+ messages in thread
* RE: [gentoo-dev] A nice idea to improve portage
@ 2003-06-10 20:15 Balaji Srinivasan
0 siblings, 0 replies; 15+ messages in thread
From: Balaji Srinivasan @ 2003-06-10 20:15 UTC (permalink / raw
To: 'tberman@gentoo.org', gentoo-dev
I agree too...having this in etc-update would be good.
Balaji
-----Original Message-----
From: Todd Berman [mailto:tberman@gentoo.org]
Sent: Tuesday, June 10, 2003 1:03 PM
To: gentoo-dev@gentoo.org
Subject: RE: [gentoo-dev] A nice idea to improve portage
On Tue, 2003-06-10 at 14:46, John Robinson wrote:
> On Tue, 2003-06-10 at 14:16, Balaji Srinivasan wrote:
> > A better idea would be if portage wrote those messages to a file and
we
> > could view it when we wanted. ie. We could have a showEbuildMessages
or some
> > such program that showed all those messages and allowed you to ack
each one.
> > I think this would be pretty useful as normally when i am fixing
things i
> > dont have time to fix all of it in one shot...
>
> I agree; that would be an excellent idea. I would, however, at least
be
> in favor of portage printing something in red at the end of an emerge
> stating that the file had been updated and needed to be looked at;
> better, if it would print the (newly added) contents of the file. Some
> of the messages printed are about crucial things that need to be done,
> often configuration changes; leaving them to be read only if one feels
> like it might leave people thinking that the messages there don't
apply
> to them.
>
> - John
Just a quick note. I agree completely that portage must somehow output
this information after a massive emerge, or store it somewhere, however,
I question the sanity of yet another small utility. We already have
etc-update, env-update, modules-update and a host of other 'small'
applications. In my experience helping people on #gentoo, one of the
most common problems is the average new gentoo user's lack of awareness
of the existence of these small helper applications.
Integrating this with etc-update or another -update application seems
like a far better idea than just writing another script.
In fact, the idea of replacing all of said applications with ONE
gentoo-update seems like something that should be approached in the near
future. Even if gentoo-update is just a shell script that calls other
shell scripts.
--Todd
--
gentoo-dev@gentoo.org mailing list
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [gentoo-dev] A nice idea to improve portage
2003-06-10 18:05 ` John Robinson
@ 2003-06-10 20:20 ` Philippe Lafoucrière
2003-06-11 3:18 ` Luke Graham
2003-06-10 21:56 ` MooktaKiNG
1 sibling, 1 reply; 15+ messages in thread
From: Philippe Lafoucrière @ 2003-06-10 20:20 UTC (permalink / raw
To: strider; +Cc: gentoo-dev
> 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. ;)
Hmmm both are good ideas !! Why don't add some README files, that are displayed
(instead of queued) at the end of an emerge ?
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [gentoo-dev] A nice idea to improve portage
2003-06-10 21:56 ` MooktaKiNG
@ 2003-06-10 21:42 ` Zach Forrest
2003-06-10 23:26 ` Kumba
0 siblings, 1 reply; 15+ messages in thread
From: Zach Forrest @ 2003-06-10 21:42 UTC (permalink / raw
To: gentoo-dev
You could also have "logmessages" FEATURE (in make.conf) that, if
enabled, logged the output of einfo, etc.
MooktaKiNG wrote:
> 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
>
>
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [gentoo-dev] A nice idea to improve portage
2003-06-10 18:05 ` John Robinson
2003-06-10 20:20 ` Philippe Lafoucrière
@ 2003-06-10 21:56 ` MooktaKiNG
2003-06-10 21:42 ` Zach Forrest
1 sibling, 1 reply; 15+ messages in thread
From: MooktaKiNG @ 2003-06-10 21:56 UTC (permalink / raw
To: gentoo-dev
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
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [gentoo-dev] A nice idea to improve portage
2003-06-10 21:42 ` Zach Forrest
@ 2003-06-10 23:26 ` Kumba
0 siblings, 0 replies; 15+ messages in thread
From: Kumba @ 2003-06-10 23:26 UTC (permalink / raw
To: Zach Forrest; +Cc: gentoo-dev
Zach Forrest wrote:
> You could also have "logmessages" FEATURE (in make.conf) that, if
> enabled, logged the output of einfo, etc.
Actually, this feature already exists. If PORT_LOGDIR is defined to a
location in /etc/make.conf, then portage will log all output to the
specified location.
--Kumba
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [gentoo-dev] A nice idea to improve portage
2003-06-10 20:20 ` Philippe Lafoucrière
@ 2003-06-11 3:18 ` Luke Graham
2003-06-11 5:10 ` Bill Kenworthy
0 siblings, 1 reply; 15+ messages in thread
From: Luke Graham @ 2003-06-11 3:18 UTC (permalink / raw
To: gentoo-dev
On Wed, 11 Jun 2003 06:20 am, Philippe Lafoucrière wrote:
> > 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. ;)
>
> Hmmm both are good ideas !! Why don't add some README files, that are
> displayed (instead of queued) at the end of an emerge ?
emerge <stuff> >output 2>&1
less output
--
luke
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [gentoo-dev] A nice idea to improve portage
2003-06-11 3:18 ` Luke Graham
@ 2003-06-11 5:10 ` Bill Kenworthy
0 siblings, 0 replies; 15+ messages in thread
From: Bill Kenworthy @ 2003-06-11 5:10 UTC (permalink / raw
To: Luke Graham; +Cc: list gentoo-dev
Have them added to /var/log/emerge.log so they are there for posterity
as well ... I think this would be a great enhancement.
BillK
On Wed, 2003-06-11 at 11:18, Luke Graham wrote:
> On Wed, 11 Jun 2003 06:20 am, Philippe Lafoucrière wrote:
> > > 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. ;)
> >
> > Hmmm both are good ideas !! Why don't add some README files, that are
> > displayed (instead of queued) at the end of an emerge ?
>
> emerge <stuff> >output 2>&1
> less output
--
Bill Kenworthy <billk@iinet.net.au>
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2003-06-11 13:34 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
-- strict thread matches above, loose matches on Subject: below --
2003-06-10 20:15 Balaji Srinivasan
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
2003-06-10 21:42 ` Zach Forrest
2003-06-10 23:26 ` Kumba
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox