Gentoo Archives: gentoo-dev

From: Markos Chandras <hwoarang@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] About using a CONFIGURATION (or SETUP) file under /usr/share/doc for configuration information
Date: Sat, 22 Dec 2012 21:47:13
Message-Id: CAG2jQ8iDdvTEE82+q-HcBnZb4AZoo1Kx5UbVfhq7T8sBCUUt8A@mail.gmail.com
In Reply to: [gentoo-dev] About using a CONFIGURATION (or SETUP) file under /usr/share/doc for configuration information by Pacho Ramos
1 On 22 December 2012 09:26, Pacho Ramos <pacho@g.o> 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 Correct me if I am wrong but are you suggesting we drop the elog
24 messages altogether? I still believe that having the elog messages
25 at the end of an 'emerge -uDN world' is more convenient. Maybe it
26 makes sense to have both, as in print the elog messages and
27 create those CONFIGURATION or SETUP files at the same time.
28
29 --
30 Regards,
31 Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2

Replies