Donnie Berkholz wrote:
On 15:35 Mon 01 Dec , Joe Peterson wrote:
However, what I see as perhaps a missing piece is more conceptual: the
important connection between the valuable info in the emerge logs (and their
somewhat transient default nature) and what a user looks for when he/she has
On 15:35 Mon 01 Dec , Joe Peterson wrote:
However, what I see as perhaps a missing piece is more conceptual: the
important connection between the valuable info in the emerge logs (and their
somewhat transient default nature) and what a user looks for when he/she has a
problem with a
Summarizing from what I've read in this thread it seems you want to find
a way to help user find information s/he doesn't look for.
If users aren't curious about their system they will sure have a hard
time figuring out how to fix it if needs be. PORTAGE_ELOG_* isn't really
that hard to find in
Gilles Dartiguelongue wrote:
As others have said, there are already proper systems, documentation and
linking through other docs. Not finding this is what I'd call lazyness
or lack of google foo. Don't misunderstand me, some stuff can get ouf of
the radar of everyone, it's ok, real people are
On Mon, 01 Dec 2008 15:35:32 -0700
Joe Peterson [EMAIL PROTECTED] wrote:
My intention with the RFC was to see if the concept has any worth and
to kick it around a bit. I do not really see this as a deficiency in
Gentoo's technology (which I have a feeling is how many here have
interpreted
I recently had a user write to me after banging his head against the
wall for a while, trying to get a package working. By the time he wrote
me, he had already figured it out, but he wanted to convey to me that
what finally helped was actually the emerge output (which stated exactly
how to get
On Sun, 30 Nov 2008 09:25:51 -0700
Joe Peterson [EMAIL PROTECTED] wrote:
Bottom line here is that there is extremely valuable and critical info
in our emerge output. In a way, these messages are like
Gentoo-specific READMEs (or release notes and/or install
instructions). However, it is not
Marius Mauch wrote:
By default, messages generated by elog, ewarn and eerror are recorded
in /var/log/portage/elog/summary.log (emerge.log is just a
transaction log, so best to ignore it here). einfo isn't recorded on
purpose as it isn't intended for important information (that's the
purpose
Seems that we already have everything you dreamed about:
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3chap=1#doc_chap4
Take a look at PORTAGE_ELOG_SYSTEM. It even can send that messages by
mail :)
HTH,
--
Peter.
В Вск, 30/11/2008 в 09:25 -0700, Joe Peterson пишет:
Bottom line
Peter Volkov wrote:
Seems that we already have everything you dreamed about:
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3chap=1#doc_chap4
Take a look at PORTAGE_ELOG_SYSTEM. It even can send that messages by
mail :)
This is all cool, indeed! :)
I suspect, however, that
On Sun, Nov 30, 2008 at 9:11 AM, Joe Peterson [EMAIL PROTECTED] wrote:
Peter Volkov wrote:
Seems that we already have everything you dreamed about:
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3chap=1#doc_chap4
Take a look at PORTAGE_ELOG_SYSTEM. It even can send that messages
Joe Peterson wrote:
Peter Volkov wrote:
Seems that we already have everything you dreamed about:
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3chap=1#doc_chap4
Take a look at PORTAGE_ELOG_SYSTEM. It even can send that messages by
mail :)
This is all cool, indeed!
Joe Peterson wrote:
Peter Volkov wrote:
Seems that we already have everything you dreamed about:
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3chap=1#doc_chap4
Take a look at PORTAGE_ELOG_SYSTEM. It even can send that messages by
mail :)
This is all cool, indeed! :)
I
13 matches
Mail list logo
