Hi, On Wed, Feb 09, 2022 at 12:23:39PM +0000, Richard Purdie wrote: > People have requested changes like this before and I rejected it as I'm > worried > that allowing people to customise this code will just fork the project into > many > different directions.
It's the other way round. There are a lot of needs to extract metadata from build system into something where reports can be generated. I'd prefer this to be buildhistory as it also tracks progress across releases and versions and custom builds if the setup has been done correctly. If this change isn't going to be accepted, projects need to continue with their custom patches on top of current buildhistory bbclass in poky. > The elif block above illustrates part of my concern since it still isn't > scaling > well and just potentially makes every buildhistory output difference (even > with > different ordering). There are reasons the data is taken from pkginfo rather > than getVar too and I think this could introduce subtle bugs in the future. The elif block is just for backwards compatibility. Changing the order of fields would be annoying in buildhistory. The new ones will be in alphabetical order so I don't think this is so bad. It is possibly to completely rewrite and simplify buildhistory but this would be annoying for users who actually track the changes. > Which variables are you actually interested in when changing this? LICENSE, CVE_PRODUCT, SRC_URI, MAINTAINER and some project specific variables too. It is very useful to have these tracked in buildhistory git repo where differences between releases can easily be seen. Cheers, -Mikko
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#161557): https://lists.openembedded.org/g/openembedded-core/message/161557 Mute This Topic: https://lists.openembedded.org/mt/89018266/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
