1 |
On Sat, 2012-12-22 at 10:26 +0100, Pacho Ramos wrote: |
2 |
> Hello |
3 |
> |
4 |
> After seeing: |
5 |
> https://bugs.gentoo.org/show_bug.cgi?id=440214 |
6 |
> |
7 |
> Looking to a lot of its blockers shows that we are using "elog" messages |
8 |
> for informing people about configuration (like pointing people to |
9 |
> external links to get proper way of configuring things, tell them to add |
10 |
> to some system groups...). I thought that maybe this kind of information |
11 |
> could be simply included in a canonical file under /usr/share/doc/ |
12 |
> package dir called, for example, CONFIGURATION or SETUP. We would them |
13 |
> point people (now with a news item, for the long term provably a note to |
14 |
> handbook to newcomers would be nice) to that file to configure their |
15 |
> setups. The main advantages I see: |
16 |
> - We will flood less summary.log ;) |
17 |
> - The information to configure the package is always present while |
18 |
> package is installed, now, if we remove merge produced logs, people will |
19 |
> need to reemerge the package or read directly the ebuild |
20 |
> |
21 |
> What do you think? |
22 |
|
23 |
I think that sounds like a perfectly acceptable solution for many of |
24 |
those. |
25 |
|
26 |
|
27 |
For layman, I ended up moving those elog messages to a layman-updater |
28 |
script (needed for something else) which was capable of knowing what |
29 |
messages were relevant to display. I run that layman-updater script in |
30 |
pkg_postinst(). |
31 |
-- |
32 |
Brian Dolbec <dolsen@g.o> |