From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-core@lists.openembedded.org
Cc: Denys Dmytriyenko <denys@ti.com>
Subject: Re: [PATCH] python3-nose: rename ${bindir}/nosetests into ${bindir}/nosetests3
Date: Tue, 16 May 2017 17:48:55 -0400 [thread overview]
Message-ID: <20170516214855.GM28053@denix.org> (raw)
In-Reply-To: <1494358314-53536-1-git-send-email-denis@denix.org>
Ping
On Tue, May 09, 2017 at 03:31:54PM -0400, Denys Dmytriyenko wrote:
> From: Denys Dmytriyenko <denys@ti.com>
>
> This resolves a conflict when both python-nose and python3-nose are pulled
> into an image and try to install ${bindir}/nosetests binary.
>
> This matches with how other distros are solving this problem, e.g. Debian:
> https://packages.debian.org/jessie/all/python3-nose/filelist
>
> Also, other packages like python3-setuptools are already doing the same with
> their binaries.
>
> Signed-off-by: Denys Dmytriyenko <denys@ti.com>
> ---
> meta/recipes-devtools/python/python3-nose_1.3.7.bb | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/meta/recipes-devtools/python/python3-nose_1.3.7.bb b/meta/recipes-devtools/python/python3-nose_1.3.7.bb
> index 99bba44..1e2ff74 100644
> --- a/meta/recipes-devtools/python/python3-nose_1.3.7.bb
> +++ b/meta/recipes-devtools/python/python3-nose_1.3.7.bb
> @@ -17,6 +17,10 @@ S = "${WORKDIR}/nose-${PV}"
>
> inherit setuptools3
>
> +do_install_append() {
> + mv ${D}${bindir}/nosetests ${D}${bindir}/nosetests3
> +}
> +
> RDEPENDS_${PN}_class-target = "\
> python3-unittest \
> "
> --
> 2.7.4
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2017-05-16 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 19:31 [PATCH] python3-nose: rename ${bindir}/nosetests into ${bindir}/nosetests3 Denys Dmytriyenko
2017-05-16 21:48 ` Denys Dmytriyenko [this message]
2017-05-17 15:22 ` Burton, Ross
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=20170516214855.GM28053@denix.org \
--to=denis@denix.org \
--cc=denys@ti.com \
--cc=openembedded-core@lists.openembedded.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