Gentoo Archives: gentoo-dev

From: Pacho Ramos <pacho@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: Wed, 09 Jan 2013 19:54:15
Message-Id: 1357761208.5230.1.camel@belkin4
In Reply to: Re: [gentoo-dev] About using a CONFIGURATION (or SETUP) file under /usr/share/doc for configuration information by Pacho Ramos
1 El lun, 07-01-2013 a las 10:34 +0100, Pacho Ramos escribió:
2 [...]
3 > This will install a README.gentoo file
4 >
5 > But there are still pending issues I don't know how to handle:
6 > - Eclass was originally oriented to cover those kind of messages that
7 > could be shown by elog first time the package is merged and, later, rely
8 > on people reading that README.gentoo
9 > - William asked for version checking support, in that case, what kind of
10 > version checking should be covered?
11 > - Should I rely on versionator.eclass or use ">/<"? I can see both forms
12 > in the tree right now
13 > - There are also a lot of "exotic" version checkings in the tree (please
14 > grep looking for REPLACING_VERSIONS to see them) that I doubt we should
15 > cover in eclass but, in that case, how to cover them also?
16 > - A suggestion about looking for "${FILESDIR}/README.gentoo" has also
17 > raised, in that case, should eclass look for either option (now
18 > DOC_CONTENTS variable or "${FILESDIR}/README.gentoo")
19 >
20
21 This changes the name of eclass to readme.gentoo.eclass and gets
22 information from ${FILESDIR}/README.gentoo
23
24 Please take a look to it

Attachments

File name MIME type
readme.gentoo.eclass text/x-readme
acpid-2.0.17.ebuild text/plain
signature.asc application/pgp-signature

Replies