On 22 December 2012 21:53, Zac Medico <zmed...@gentoo.org> wrote: > On 12/22/2012 01:46 PM, Markos Chandras wrote: >> 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? I still believe that having the elog messages >> at the end of an 'emerge -uDN world' is more convenient. Maybe it >> makes sense to have both, as in print the elog messages and >> create those CONFIGURATION or SETUP files at the same time. > > As a compromise, you could have the ebuild trigger the elog message only > when there is not a previous version of the package installed. > -- > Thanks, > Zac >
Well yeah, plus the elog messages are logged in /var/log/portage/elog so duplicating them in /usr/share/doc/$PF/SETUP does not make much sense to me :/ -- Regards, Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
