Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Dominic Sacré" <dominic.sacre@gmx.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/4] python3: remove package python3-robotparser
Date: Sun, 09 Aug 2015 12:58:38 +0200	[thread overview]
Message-ID: <55C7325E.5050305@gmx.de> (raw)
In-Reply-To: <BC8B57D1-2220-435B-A2BA-6B0211E13907@gmail.com>

On 2015-08-09 03:02, Khem Raj wrote:
>> On Jul 28, 2015, at 7:58 AM, Dominic Sacré <dominic.sacre@gmx.de> wrote:
>>
>> robotparser has been moved to urllib.robotparser in Python 3, and gets
>> packaged as part of python3-netclient alongside the rest of urllib.
>> This causes python3-modules to depend on an empty/missing
>> python3-robotparser package.
>>
>> robotparser.py is relatively small and has no dependencies outside
>> urllib, so it makes more sense to eliminate the python3-robotparser
>> package than to alter the manifest for python3-netclient.
>>
>> Part of the fix for [YOCTO #8048].
>>
>> Signed-off-by: Dominic Sacré <dominic.sacre@gmx.de>
>> ---
>> meta/recipes-devtools/python/python-3.4-manifest.inc | 10 +++-------
>> scripts/contrib/python/generate-manifest-3.4.py      |  3 ---
>> 2 files changed, 3 insertions(+), 10 deletions(-)
>>
>> diff --git a/meta/recipes-devtools/python/python-3.4-manifest.inc b/meta/recipes-devtools/python/python-3.4-manifest.inc
>> index 557acdf..77f0125 100644
>> --- a/meta/recipes-devtools/python/python-3.4-manifest.inc
>> +++ b/meta/recipes-devtools/python/python-3.4-manifest.inc
> 
> this file is auto generated. So did you regenerate it ?

The changes to scripts/contrib/python/generate-manifest-3.4.py are
included in the same patch:

>> diff --git a/scripts/contrib/python/generate-manifest-3.4.py b/scripts/contrib/python/generate-manifest-3.4.py
>> index 569fd3c..42c851c 100755
>> --- a/scripts/contrib/python/generate-manifest-3.4.py
>> +++ b/scripts/contrib/python/generate-manifest-3.4.py
>> @@ -343,9 +343,6 @@ if __name__ == "__main__":
>>     m.addPackage( "${PN}-shell", "Python shell-like functionality", "${PN}-core ${PN}-re",
>>     "cmd.* commands.* dircache.* fnmatch.* glob.* popen2.* shlex.* shutil.*" )
>>
>> -    m.addPackage( "${PN}-robotparser", "Python robots.txt parser", "${PN}-core ${PN}-netclient",
>> -    "urllib/robotparser.*")
>> -
>>     m.addPackage( "${PN}-subprocess", "Python subprocess support", "${PN}-core ${PN}-io ${PN}-re ${PN}-fcntl ${PN}-pickle",
>>     "subprocess.*" )

I ran the modified script to update python-3.4-manifest.inc, then
added both files to my commit. Is there something I've missed?


Dominic


  reply	other threads:[~2015-08-09 10:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28 14:58 [PATCH 0/4] python3: fix building extension modules, make python3-modules installable Dominic Sacré
2015-07-28 14:58 ` [PATCH 1/4] python3: detect libraries in STAGING_LIBDIR Dominic Sacré
2015-07-28 14:58 ` [PATCH 2/4] python3: remove package python3-robotparser Dominic Sacré
2015-08-09  1:02   ` Khem Raj
2015-08-09 10:58     ` Dominic Sacré [this message]
2015-07-28 14:58 ` [PATCH 3/4] python3: remove 2to3 symlink from package python3-2to3 Dominic Sacré
2015-07-28 14:58 ` [PATCH 4/4] python3: delete patches that don't get applied anywhere Dominic Sacré

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=55C7325E.5050305@gmx.de \
    --to=dominic.sacre@gmx.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox