public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joerg Bornkessel <hd_brummy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] eclass/vdr-plugin-2.eclass EAPI=6 changes, plz review
Date: Sun, 29 May 2016 18:49:22 +0200	[thread overview]
Message-ID: <574B1D92.7070303@astrali.lan> (raw)
In-Reply-To: <20160526111647.29f280d5.mgorny@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Am 26.05.2016 um 11:16 schrieb Michał Górny:
> Since you already committed it with all the todos inside, just the
> important thing.
> 
> On Sun, 22 May 2016 23:21:59 +0200 Joerg Bornkessel
> <hd_brummy@gentoo.org> wrote:
> 
>> - -   local docfile - -   for docfile in README* HISTORY
>> CHANGELOG; do - -       [[ -f ${docfile} ]] && dodoc ${docfile} +
>> local commondoc=( README* HISTORY CHANGELOG ) +   for docfile in
>> "${commondoc[@]}"; do +       if [[ ${EAPI} == "6" ]]; then +
>> local DOCS="${DOCS} ${docfile}" +           [[ -f ${docfile} ]]
>> && einstalldocs "${DOCS[@]}" +       else +           [[ -f
>> ${docfile} ]] && dodoc ${docfile} +       fi
> 
> I have no clue what you're trying to achieve ...


Oh please, forget this crap!
After rereading einstalldocs, how it works and how is it to handle in
.ebuild, here my simple rewrite to integrate it in EAPI=6

<snipp>

    if [[ ${EAPI} != [45] ]]; then
        einstalldocs
    else
        local docfile
            for docfile in README* HISTORY CHANGELOG; do
                [[ -f ${docfile} ]] && dodoc ${docfile}
            done
    fi

</snapp>

yepp, einstalldocs is supported in EAPI=5 from eutils.eclass too,
but i will leave it untached as we use it in this way for EAPI=4,5
since long time.
So we are save in the existing eapi=4,5 supported ebuilds in the tree.

Thanks for your review and reply

Cheers

/dev/joerg

- -- 
Joerg Bornkessel <hd_brummy@gentoo.org>
GnuPG Key: 0x93EB5F4DAA5832A1
Fingerprint: 0E0A A1EE 1DF4 41D7 A3F5  21C2 93EB 5F4D AA58 32A1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.1
Comment: Signed-off-by: Jörg Bornkessel <hd_brummy@gentoo.org>

iQJ8BAEBCgBmBQJXSx2JXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwRTBBQTFFRTFERjQ0MUQ3QTNGNTIxQzI5
M0VCNUY0REFBNTgzMkExAAoJEJPrX02qWDKhRsIP/3+PiGzWmlWfns0THCVjM2cb
xstNG7P+qKSFyWD9tgmSeGLsp590wh8bDBh8LWGfEPayYgal5ps1FeEdSS+syND6
fBk8QcBBZlPUSupg4f0sNsOmOguvXDhYz8u9PX2yfbTWAiOSWQcjUyvzU2FascrZ
bsCDhpEbDFbjS/vZJs52XCQhxU3WTFzchdn1+87JxDGslyMFe5+DojbDYeJLmkPK
9EeZ938PRAuaVNd28fE9A8YbueP59vvtL4oyTab/sWRv/FXsuFJbPlTd2+pOTYWJ
EVRvQ9kUiHR+PX3T1m5m8KGa8ZEKR5O/2ibcwI8jlSpOM287/rypujjT+pycpz8A
yQ+CF8L8g/SQZRyl3GAYrA/FhHRHXXskbBQOrELk+PywXS/7ccSIV+ySWdawf8UV
gItXrWaFZDD6TjG08oXdp5IC1yMh2Vzna7GTPXUoYHJnDp4aZj6ZX0Z+zRRvSIGG
MXRYsOMfpPWQOxpczD+oMuC973tv+Psr0c8gisKmK8ZEtdqVj2ZVtRRg/Jig7RhH
qAmxMBVhxAYe8m/vSRfJC4zT2GmSZLbFAOKoy5r0Gc5t/PVvHDax2Ku46SpMuWSr
gaWOcKTyZC+ynazduEIj4ZNKZhDEWnVx+OjcIVwPDV4cxRiHFVr2tuQK1Un8JXsu
8tuGDeoMd24HPEjuD5JA
=oSFD
-----END PGP SIGNATURE-----


  reply	other threads:[~2016-05-29 16:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16  9:39 [gentoo-dev] eclass/vdr-plugin-2.eclass EAPI=6 changes, plz review Joerg Bornkessel
2016-05-17  6:17 ` Michał Górny
2016-05-22 21:21   ` Joerg Bornkessel
2016-05-26  9:16     ` Michał Górny
2016-05-29 16:49       ` Joerg Bornkessel [this message]
2016-05-29 17:21         ` Michał Górny

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=574B1D92.7070303@astrali.lan \
    --to=hd_brummy@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