From: "Michał Górny" <mgorny@gentoo.org>
To: "M. J. Everitt" <m.j.everitt@iee.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal for enhancement to PMS/EAPI7+
Date: Wed, 18 May 2016 08:43:08 +0200 [thread overview]
Message-ID: <20160518084308.21ea0b28.mgorny@gentoo.org> (raw)
In-Reply-To: <573BDC5B.9080404@iee.org>
[-- Attachment #1: Type: text/plain, Size: 1334 bytes --]
On Wed, 18 May 2016 04:07:07 +0100
"M. J. Everitt" <m.j.everitt@iee.org> wrote:
> I've just been party to a discussion over in the Proxy Maintainers
> channel .. and the subject of correct ways to install documentation
> popped up. It seems to me rather quirky, that there is no middle ground
> in (for example) EAPI6 to have the default documentation installed per
> https://dev.gentoo.org/~ulm/pms/head/pms.html#x1-144003r4 , PLUS maybe
> another folder or file(s). The existing framework ONLY allows *either*
> /only/ the default documentation *or* an override through the DOCS=
> variable.
>
> My idea thus, was inspired by the simple bash DOCS+= ( ) statement, that
> would allow you to append files/folders to the installdocs list,
> assuming that DOCS was pre-populated with an existing set of files.
> Obviously the status quo is set for EAPI6 and algorithms defined, but
> wondered if it could be considered for a future update/improvement cycle?!
How is this going to work? In order to pre-populate it, you need to
know the list of files. And the list of files isn't known until
src_install(). In fact, with the current behavior it's not even known
before einstalldocs is actually called, and changing that could break
stuff.
--
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
next prev parent reply other threads:[~2016-05-18 6:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 3:07 [gentoo-dev] Proposal for enhancement to PMS/EAPI7+ M. J. Everitt
2016-05-18 5:40 ` Ulrich Mueller
2016-05-18 5:44 ` Kent Fredric
2016-05-18 5:57 ` Sam Jorna
2016-05-18 6:37 ` Ulrich Mueller
2016-05-18 6:43 ` Michał Górny [this message]
2016-05-18 6:48 ` M. J. Everitt
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=20160518084308.21ea0b28.mgorny@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=m.j.everitt@iee.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