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