| 1 |
El sáb, 22-12-2012 a las 21:46 +0000, Markos Chandras escribió: |
| 2 |
> On 22 December 2012 09:26, Pacho Ramos <pacho@g.o> wrote: |
| 3 |
> > Hello |
| 4 |
> > |
| 5 |
> > After seeing: |
| 6 |
> > https://bugs.gentoo.org/show_bug.cgi?id=440214 |
| 7 |
> > |
| 8 |
> > Looking to a lot of its blockers shows that we are using "elog" messages |
| 9 |
> > for informing people about configuration (like pointing people to |
| 10 |
> > external links to get proper way of configuring things, tell them to add |
| 11 |
> > to some system groups...). I thought that maybe this kind of information |
| 12 |
> > could be simply included in a canonical file under /usr/share/doc/ |
| 13 |
> > package dir called, for example, CONFIGURATION or SETUP. We would them |
| 14 |
> > point people (now with a news item, for the long term provably a note to |
| 15 |
> > handbook to newcomers would be nice) to that file to configure their |
| 16 |
> > setups. The main advantages I see: |
| 17 |
> > - We will flood less summary.log ;) |
| 18 |
> > - The information to configure the package is always present while |
| 19 |
> > package is installed, now, if we remove merge produced logs, people will |
| 20 |
> > need to reemerge the package or read directly the ebuild |
| 21 |
> > |
| 22 |
> > What do you think? |
| 23 |
> |
| 24 |
> Correct me if I am wrong but are you suggesting we drop the elog |
| 25 |
> messages altogether? |
| 26 |
|
| 27 |
No, only to drop its usage for configuration stuff (like that kind of |
| 28 |
message telling you to go to page XXXX to know how to configure your |
| 29 |
app) |
Archives