Open points about moving the dependencies from the internal to the external repo.

[Claudius Heine]

Hi,

I am have some questions about efibootguard:

- Do we plan to have some kind of versioning for it?
- Should we tag revisions on github?
- I suppose those questions are answered with yes, when will that be
done?
- Should we release a `meta-efibootguard` for easy oe integration?

Cheers,
Claudius


--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: c...@denx.de

PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
Keyserver: hkp://pool.sks-keyservers.net

[Jan Kiszka]

On 2017-06-29 09:42, Claudius Heine wrote:
> Hi,
>
> I am have some questions about efibootguard:
>
> - Do we plan to have some kind of versioning for it?
> - Should we tag revisions on github?
> - I suppose those questions are answered with yes, when will that be
> done?

I'm waiting for the dust to settle, but I could also imagine tagging the
current state (next, after merging to master) as some v0.3.

> - Should we release a `meta-efibootguard` for easy oe integration?

That would surely be interesting. How much of such a layer would be
board-agnostic? Or should we rather start off with enabling meta-iot2000
with demo recipes that people can adopt for their own projects?

A third option, specifically if there is only little common code, would
be trying to sneak into meta-openembedded. No idea about their
acceptance process yet, though.

Jan

--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux

[Claudius Heine]

Hi,

On 06/29/2017 11:00 AM, [ext] Jan Kiszka wrote:
> On 2017-06-29 09:42, Claudius Heine wrote:
>> Hi,
>>
>> I am have some questions about efibootguard:
>>
>> - Do we plan to have some kind of versioning for it?
>> - Should we tag revisions on github?
>> - I suppose those questions are answered with yes, when will that be
>> done?
>
> I'm waiting for the dust to settle, but I could also imagine tagging the
> current state (next, after merging to master) as some v0.3.
>
>> - Should we release a `meta-efibootguard` for easy oe integration?
>
> That would surely be interesting. How much of such a layer would be
> board-agnostic? Or should we rather start off with enabling meta-iot2000
> with demo recipes that people can adopt for their own projects?

AFAIKT its just two wic plugins, a recipe and a bbclass and all of that
is currenty not iot2000 specific.

Cheers,
Claudius