| 1 |
There is already a logging facility that logs to /var/log/emerge.log |
| 2 |
that can provide a"place" to log the messages. Why not just print the |
| 3 |
messages there so a history is developed - seems the appropriate place |
| 4 |
to me. |
| 5 |
|
| 6 |
BillK |
| 7 |
|
| 8 |
|
| 9 |
On Wed, 2004-11-17 at 03:38 +0100, Alexander Gretencord wrote: |
| 10 |
> On Tuesday 16 November 2004 21:14, Ciaran McCreesh wrote: |
| 11 |
> > 1. This isn't up to any Gentoo developer. There are only four of them |
| 12 |
> > who could commit this. |
| 13 |
> |
| 14 |
> ok, portage developer :) |
| 15 |
> |
| 16 |
> > 2. The community provided solutions are inadequate. |
| 17 |
> |
| 18 |
> ... |
| 19 |
> |
| 20 |
> > 3. You *really* don't want every einfo logged. Trust me, I already do |
| 21 |
> > this, and it's messy. einfo wasn't designed to be logged, it was |
| 22 |
> > designed to display a message to the user during a build. |
| 23 |
> |
| 24 |
> It would be enough to have all the einfos in one place, _after_ merging all |
| 25 |
> packages is done for a start. |
| 26 |
> |
| 27 |
> > It'd be a heck of a lot easier to go through and convert those few critical |
| 28 |
> > messages to use a function like 'elog' or somesuch. |
| 29 |
> |
| 30 |
> So we'd have einfo, eerror, ewarn and everyimportanzupgrademessage? :) |
| 31 |
> |
| 32 |
> |
| 33 |
> Alex |
| 34 |
> |
| 35 |
> -- |
| 36 |
> gentoo-dev@g.o mailing list |
| 37 |
> |
| 38 |
|
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-dev@g.o mailing list |
Archives