Add the ExtendedVersion to MANIFEST file and os-release

[Adriana Kobylak]

Hi Chanh,

I don’t see any issues. I’d say go ahead and submit the changes to add this new field to the MANIFEST and os-release, with a value set to an empty string as default, which can then be filled in as needed for different systems that want it. Then the bmc-code-mgmt repo can use this new info to create the Extended Version d-bus object.

Thanks.

> On Jan 12, 2021, at 9:51 PM, Chanh Nguyen OS <chanh at os.amperecomputing.com> wrote:
> 
> This Message Is From an External Sender
> This message came from outside your organization.
>  <>Hi all,
> 
> I'm supporting the ExtendedVersion in phosphor-bmc-code-mgmt. You can see more at https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-bmc-code-mgmt/+/39406 <https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-bmc-code-mgmt/+/39406> 
> 
> I would like to add the ExtendedVersion field to the MANIFEST and store at os-release. So, I send this mail to discuss the new field name and the value in MANIFEST, os-release. I suggest 
> 
> The new field name in MANIFEST is ExtendedVersion . It will like as:
> purpose 
> version
> ExtendedVersion
> KeyType 
> HashType
> MachineName
> The new field name in os-release is EXTENDED_VERSION 
> ID
> NAME
> VERSION
> VERSION_ID
> PRETTY_NAME
> BUILD_ID
> OPENBMC_TARGET_MACHINE
> EXTENDED_VERSION
> The "ExtendedVersion" value will be similar to the "MACHINE" field. It is typically set in the openbmc/meta-*/meta-MACHINE/conf/local.conf.sample file.
> Please raise your ideas for this design! 
> 
> Thank you!
> Chanh

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20210122/d87cb82e/attachment-0001.htm>