1 |
At the risk of starting a flame war, two minor netiquette tips... ;) |
2 |
|
3 |
1) Top or mid-posting is not recommended .. makes following the thread |
4 |
harder [note my deliberate misuse here!] |
5 |
2) PLEASE PLEASE sort out your clock .. I have emails from you (yeah I |
6 |
know Thunderbird is ****) from the future year 2026 which don't really |
7 |
belong at the top of my mail folder..... |
8 |
|
9 |
Tyvm,ia, |
10 |
|
11 |
Michael. |
12 |
PS. Yes, I was aware of the elogv package, I think its mentioned in |
13 |
whatever docs for PORTAGE_ELOG_*. If it needs updating for EAPI6 we'll |
14 |
have to hunt down a maintainer.... |
15 |
|
16 |
On 11/12/16 15:49, james wrote: |
17 |
> On 12/14/2016 12:59 PM, Doug Freed wrote: |
18 |
>> On Wed, Dec 14, 2016 at 10:45 AM, Rich Freeman <rich0@g.o> wrote: |
19 |
>>> On Wed, Dec 14, 2016 at 10:27 AM, M. J. Everitt |
20 |
>>> <m.j.everitt@×××.org> wrote: |
21 |
>>>> |
22 |
>>>> I do, but only usually if its the last package of an emerge because |
23 |
>>>> otherwise its lost many many thousands of lines upwards. Thank |
24 |
>>>> goodness |
25 |
>>>> for portage's savelog feature. - Actually that reminds me .. someone |
26 |
>>>> mentioned a useful tweak to that, with an appropriate FEATURES switch, |
27 |
>>>> it would categorise the output of the logging system .. must look that |
28 |
>>>> one up again, or poke the wiki team ....... |
29 |
> |
30 |
> |
31 |
> |
32 |
> |
33 |
> Well pardon me, if I'm miss interpreting here, as there is only this |
34 |
> fragmented thread in my inbox:: no prior postings. But perhaps folks |
35 |
> should look at "app-portage/elogv" |
36 |
> |
37 |
> Already in place, easy to use, and should be updated with EAPI (5/6) |
38 |
> based parsing features? |
39 |
> |
40 |
> hth, |
41 |
> James |
42 |
> |
43 |
> |
44 |
>>>> |
45 |
>>> |
46 |
>>> IMO, emailing elogs to root should probably be the default. By all |
47 |
>>> means let people turn it off, but I bet a lot of people don't realize |
48 |
>>> it is an option. |
49 |
>> |
50 |
>> Having just looked at portage's mail code, you can't use the mail |
51 |
>> subsystem if you have no mailserver or sendmail binary. Instead, |
52 |
>> it'll just throw an error, so you couldn't have any default Portage |
53 |
>> configuration to mail them somewhere. The current default |
54 |
>> configuration appends to ${PORT_LOGDIR}/elog/summary.log with qa, log, |
55 |
>> warn, and error levels for every package that outputs any of these |
56 |
>> classes. If PORT_LOGDIR is unset, the target is |
57 |
>> /var/log/portage/elog/summary.log. |
58 |
>> |
59 |
>>> |
60 |
>>> This goes in all my make.conf files: |
61 |
>>> PORTAGE_ELOG_CLASSES="warn error log" |
62 |
>>> PORTAGE_ELOG_SYSTEM="save mail" |
63 |
>>> PORTAGE_ELOG_MAILURI="a@×.com smtp.server.address" |
64 |
>>> PORTAGE_ELOG_MAILSUBJECT="package \${PACKAGE} merged on \${HOST} |
65 |
>>> with notice" |
66 |
>>> |
67 |
>>> Yes, some packages are a bit spammy and this should be fixed, but in |
68 |
>>> general it has prevented more headaches than it has caused. |
69 |
>> |
70 |
>> This can't really be fixed in a good way, and I'd really rather it |
71 |
>> wasn't anyway. A [ -z "$REPLACING_VERSIONS" ] test is only valid in |
72 |
>> pkg_* phases (and by PMS, REPLACING_VERSIONS doesn't have to be |
73 |
>> defined in pkg_pretend or pkg_setup), and in many cases, using |
74 |
>> REPLACING_VERSIONS in any way can be difficult to do correctly. Using |
75 |
>> the readme.gentoo eclass wouldn't be an awful way to go if it really |
76 |
>> bothers you, but you could also use mail_summary instead of mail to |
77 |
>> reduce the mail spam to 1 email per emerge run. |
78 |
>> |
79 |
>> -Doug |
80 |
>> |
81 |
>> |
82 |
> |
83 |
> |