Hi Chris
Sunday 03 Sep 2017 16:56:08, Chris Mayo wrote :
> ---
> Please consider this clarification of optfeature.
>
> Chris
>
> eclass/eutils.eclass | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/eclass/eutils.eclass b/eclass/eutils.eclass
> index
On 09/06/2017 02:39 PM, Chris Mayo wrote:
>
> I believe @EXAMPLE is only for the first documentation block introducing the
> eclass.
>
> At least where it is used for functions the text doesn't show up in the man
> page.
> e.g. prefix.eclass hprefixify() and prefixify_ro()
>
Looks like
On 03/09/17 22:22, Michael Orlitzky wrote:
> On 09/03/2017 11:56 AM, Chris Mayo wrote:
>> #
>> # The following snippet would suggest app-misc/foo for optional foo support,
>> # app-misc/bar or app-misc/baz[bar] for optional bar support
>>
>
> Would the @EXAMPLE tag[0] make sense here?
>
>
>
On 09/03/2017 11:56 AM, Chris Mayo wrote:
> #
> # The following snippet would suggest app-misc/foo for optional foo support,
> # app-misc/bar or app-misc/baz[bar] for optional bar support
>
Would the @EXAMPLE tag[0] make sense here?
[0] https://devmanual.gentoo.org/eclass-writing/index.html
---
Please consider this clarification of optfeature.
Chris
eclass/eutils.eclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/eclass/eutils.eclass b/eclass/eutils.eclass
index fe4339f6b89..f35fa5980d7 100644
--- a/eclass/eutils.eclass
+++ b/eclass/eutils.eclass
@@
