List Archive: gentoo-dev
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 package. Yes, users will realize this as they use Gentoo (and
> will start paying more attention to logs as a result), so I don't think it's a
> huge problem, but what this particular user said to me made me think that
> there is, perhaps, an opportunity to improve the situation.
Based on the rarity of me seeing this reported as a problem, I'm
inclined to think it says more about this user than about our system. I
don't think it's our responsibility to put documentation everywhere
someone might conceivably look for information.
--
Thanks,
Donnie
Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com
|
| Replies: |
Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official
-- Joe Peterson
|
| References: |
[RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official
-- Joe Peterson
|
Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official
-- Gilles Dartiguelongue
|
Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official
-- Joe Peterson
|
| Navigation: |
|
Lists:
gentoo-dev:
< Prev
By Thread
Next >
< Prev
By Date
Next >
|
| Previous by thread: |
| Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official |
| Next by thread: |
| Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official |
| Previous by date: |
| Re: EAPI 2 policy for portage tree |
| Next by date: |
| Re: Proposal for how to handle stable ebuilds |
|