[OE-core] Sorting rootfs manifest with .ipk packaging

[Christopher Larson]

On Thu, Oct 1, 2015 at 11:57 AM, Otavio Salvador <
otavio.salvador at ossystems.com.br> wrote:

> On Thu, Oct 1, 2015 at 3:55 PM, Andre McCurdy <armccurdy at gmail.com> wrote:
> > On Wed, Sep 30, 2015 at 5:48 PM, Khem Raj <raj.khem at gmail.com> wrote:
> >>
> >>> On Sep 30, 2015, at 3:03 PM, Andre McCurdy <armccurdy at gmail.com>
> wrote:
> >>>
> >>> I'd like the rootfs manifest to be sorted when using .ipk packaging.
> >>> Would a patch to sort the result of OpkgPkgsList().list be acceptable?
> >>> Or would the sorting be better done elsewhere?
> >>
> >> its not clear what kind of sorting are you looking for. It could be a
> good thing in general if its
> >> configurable and you can explain the value add of doing it.
> >
> > Aim is to make the manifest for each rootfs a little more human
> > readable by sorting the list of installed packages alphabetically.
> >
> > Currently, when ipk packaging is used, the order of packages in the
> > manifest matches the order in /var/lib/opkg/status, which appears to
> > be "random".
> >
> > It looks like RpmPkgsList().list does always sort it's results before
> > returning, so adding a sort to OpkgPkgsList().list would make it
> > consistent with the RPM equivalent.
>
> Consistency is always good. So please prepare a patch.


Agreed. In addition to being more human readable, it'd also be slightly
easier to compare manifests if they're pre-sorted with a tool like 'comm'.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20151001/894c6d6c/attachment-0002.html>