From: Austin English <wizardedit@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Default DOCS for einstalldocs and HACKING file
Date: Tue, 7 Jun 2016 18:59:42 -0500 [thread overview]
Message-ID: <57575FEE.70205@gentoo.org> (raw)
In-Reply-To: <57575693.5040803@iee.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 06/07/2016 06:19 PM, M. J. Everitt wrote:
> On 07/06/16 23:50, NP-Hardass wrote:
>> From what I've seen, HACKING is a fairly common doc in FOSS projects.
>> It doesn't seem to have been included in the default DOCS for
>> einstalldocs in EAPI6. While going through the MATE packages, I noticed
>> that we have quite a few packages that include HACKING in DOCS, so I
>> cannot delete the DOCS array and take advantage of the automagic doc
>> detection feature of einstalldocs.
>>
>> Does anyone know why we omitted this file from the default DOCS? A
>> quick grep of the main repo shows ~370 ebuilds with HACKING listed. Is
>> this file no longer considered worthy of being included by default in
>> our installed docs? If so, looking for advice on whether it is worth
>> keeping or dropping that file from my packages?
>>
> I made the suggestion a while back in IRC that it would be nice if there
> was a way to append to the DOCS array in an ebuild, rather than have to
> override it, and remember the standard list every time, or just lose the
> extra file(s). Unfortunately I was laughed out of the channel. So,
> whilst it would probably be something for another EAPI change .. what do
> readers think of the idea of an EXTRA_DOCS variable or similar method
> for doing this, for exactly this reason/purpose??
>
> MJE
Some way to append docfiles would be very welcome IMO.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJXV1/uAAoJEACzKVe5S/PhQuAP/0OZxgfG5tD9IrBV+8VulPr7
TbVq+XITJ3iNwHIvVtZdW65Us+RGJ+oVSET8EroWhUxMV5udjVsphKQ6kXiV6Uc9
IehRKTBeXnwzzhke853xBvV0WLGxQECj3zqpDfHUpaODeR5IB7zvw3qAnhzzaHYQ
QPKuvHm1l1rRIqeHqXY/6kd8DJrCXY1YsF7P1FwYZznmUUGGC1+bYt70rY1OJ6qG
P/SM/fe8C1BTtXQpFDacE6f76fs5AT9MaC9a3/fr6UAiYlKz7bL7l+kzTjHpwuf/
yQGlL9Xc2Cp3zUoXp3zN0Zf+jhxsPvL/4LVv/BPY4IvNFBGCBzBD7Lqv1ootDlZM
HNBcdZV7opz5T8/nCTN35iA1KHgvTxsWwF/vFjtSbaxF4lnhw3OQSFPz6iILQFnj
Xo/7rjw4y4HFBe5BzYujjvl2dDeXfJpEAr9KaOj4yuUpLB1RBLZ2+/uhkcwl5Tp7
pTKG9yKjKOze43fwXITtD8ALCmR3Jn9haMyku9NLiRDr8hKKvSTDC3xeAHeEMMuN
RG9yDrqhfp/rtU3WKCo6hnJ300YJxRm12ltbSqXJEdaVdv2vLoIKJUfaGmGhAHaz
dHtOHjolLI8jjhRsv4bgSYXbQOSJzU/gy2ZsJsHgGibRiRLloe6z8he9RrjaImZB
N+y8gnQjT8GObWtDmiXn
=gTUn
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-06-08 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 22:50 [gentoo-dev] Default DOCS for einstalldocs and HACKING file NP-Hardass
2016-06-07 23:19 ` M. J. Everitt
2016-06-07 23:59 ` Austin English [this message]
2016-06-08 6:39 ` Michał Górny
2016-06-08 20:22 ` Daniel Campbell
2016-06-08 6:40 ` Michał Górny
2016-06-09 4:54 ` NP-Hardass
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57575FEE.70205@gentoo.org \
--to=wizardedit@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox