All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-security][master][warrior][PATCH 3/3] python3-scapy: solved the conflict with python-scapy
Date: Mon, 10 Jun 2019 11:09:30 +0300	[thread overview]
Message-ID: <20190610080930.GA5894@localhost> (raw)
In-Reply-To: <20190610072424.14779-4-zangrc.fnst@cn.fujitsu.com>

On Mon, Jun 10, 2019 at 03:24:24PM +0800, Zang Ruochen wrote:
> -Rename the following file to resolve the conflict with python-scapy:
> 	Rename /usr/bin/UTscapy to /usr/bin/UTscapy3
> 	Rename /usr/bin/scapy to /usr/bin/scapy3
> 
> Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
> ---
>  recipes-security/scapy/python3-scapy_2.4.2.bb | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/recipes-security/scapy/python3-scapy_2.4.2.bb b/recipes-security/scapy/python3-scapy_2.4.2.bb
> index 83c79f4..abcaeeb 100644
> --- a/recipes-security/scapy/python3-scapy_2.4.2.bb
> +++ b/recipes-security/scapy/python3-scapy_2.4.2.bb
> @@ -3,3 +3,7 @@ require python-scapy.inc
>  
>  SRC_URI += "file://run-ptest"
>  
> +do_install_append() {
> +        mv ${D}${bindir}/scapy ${D}${bindir}/scapy3
> +        mv ${D}${bindir}/UTscapy ${D}${bindir}/UTscapy3
> +}

A proper solution would require using alternatives so that installing 
either the python2 or the python3 version would provide the binary.

But given that python2 is reaching end of life I would suggest to just 
rename the python2 binaries and keep the python3 binaries that will stay
long-term at their upstream names.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  reply	other threads:[~2019-06-10  8:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10  7:24 [meta-security][master][warrior][PATCH 0/3] python-scapy:solved the conflict with python3-scapy Zang Ruochen
2019-06-10  7:24 ` [meta-security][master][warrior][PATCH 1/3] python-scapy: Remove redundant sed operations Zang Ruochen
2019-06-10  7:24 ` [meta-security][master][warrior][PATCH 2/3] python-scapy: solved the conflict with python3-scapy Zang Ruochen
2019-06-10  7:24 ` [meta-security][master][warrior][PATCH 3/3] python3-scapy: solved the conflict with python-scapy Zang Ruochen
2019-06-10  8:09   ` Adrian Bunk [this message]
2019-06-10 14:48 ` [meta-security][master][warrior][PATCH 0/3] python-scapy:solved the conflict with python3-scapy akuster808

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=20190610080930.GA5894@localhost \
    --to=bunk@stusta.de \
    --cc=yocto@yoctoproject.org \
    --cc=zangrc.fnst@cn.fujitsu.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.