On Fri, 4 Jan 2013 23:34:59 -0600 Donnie Berkholz <dberkh...@gentoo.org> wrote:
> On 10:26 Sat 22 Dec , Pacho Ramos 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? > > Bikeshedding ... would go with README.gentoo, because people are > already used to looking for README files. Every time we can eliminate > Gentoo-specific weirdness, we should. > See the documentation for README.Debian[1], most importantly the example. ;) I'd say we should handle it the same as Debian does. What could we possibly gain from doing it differently? [1] http://www.debian.org/doc/manuals/maint-guide/dother.en.html#readme
signature.asc
Description: PGP signature
