[yocto] [opkg-utils][PATCH 00/22] Partially prepare for python3 and fix old Packages file reuse
Koen Kooi
koen at beagleboard.org
Fri Apr 27 05:42:40 PDT 2012
Op 27 apr. 2012, om 08:39 heeft Koen Kooi het volgende geschreven:
>
> Op 26 apr. 2012, om 20:52 heeft Martin Jansa het volgende geschreven:
>
>> On Thu, Apr 26, 2012 at 06:21:45PM +0200, Koen Kooi wrote:
>>>
>>> Op 26 apr. 2012, om 12:43 heeft Richard Purdie het volgende geschreven:
>>>
>>>> On Fri, 2012-03-30 at 00:21 +0200, Martin Jansa wrote:
>>>>> First 5 patches are taken from oe-core.
>>>>>
>>>>> Then there are some cleanups and fixes for issues I've found while looking
>>>>> for cause of very long package-index calls.
>>>>>
>>>>> Some patches uses compatible changes from 2to3 (tested with python2.7), but
>>>>> python3 support is not 100% complete, but were closer.
>>>>>
>>>>> And in the end I've found the cause.. printing long fields (e. g. description)
>>>>> with opkg.py was producing empty lines in Packages file (which are Packages entry
>>>>> separators) so only first entries till first empty line were processed from old
>>>>> Packages file and the rest was always extracted from control files in packaged .ipk.
>>>>>
>>>>> And this also fixes Packages.filelist generation.
>>>>>
>>>>> I don't use python very much, so please review.
>>>>>
>>>>> And the speedup? Almost 60 times :)
>>>
>>> [..]
>>>
>>>> I reviewed these and they all look like good improvements. I've merged
>>>> it into master, thanks!
>>>
>>> After some more time in oe-core master for testing we should seriously consider cherry-picking the SRCREV bump to the denzil branch.
>>
>> Agreed, saves about 4 hours per day (13 images each with own package-index run
>> and extra run for feed if built after iamges) on my buildhost for last month or so :)
>
> I merged in denzil-next locally and grabbed 26465 from patchwork. Let's see how much time it saves on my machine :)
With a relatively small deploy area: 7 minutes saved per image build!
More information about the yocto
mailing list