search

commontorizon / meta-common-torizon

Fork of the TorizonCore OpenEmbedded Distro Layer to create Common TorizonCore
MIT License
10 stars 10 forks source link

Monstrous Rebase #15

Closed leonheldattoradex closed 11 months ago

leonheldattoradex commented 11 months ago

This PR is just meant to track changes between meta-toradex-torizon and common. Let's build the images and test it out.

leonheldattoradex commented 11 months ago

@microhobby for the manifest, which commit should I use? I'm not sure what's the strategy between the official and common releases.

microhobby commented 11 months ago

@microhobby for the manifest, which commit should I use? I'm not sure what's the strategy between the official and common releases.

@leonheldattoradex you can get from https://git.toradex.com/cgit/toradex-manifest.git that was from where we forked it and then rebase the existent files and update the common one.

leonheldattoradex commented 11 months ago

@microhobby that I get, what is a bit confusing is should I use https://github.com/commontorizon/meta-common-torizon/pull/15/commits/7afae1ca288061ad99af07a4dd996bc4d56288a6 for https://github.com/commontorizon/commontorizon-manifest/blob/kirkstone/torizoncore/common.xml#L92?

How exactly should we decide which commit from meta-common-torizon to base the release from?

microhobby commented 11 months ago

@leonheldattoradex nope, this will be updated after the merge here with the top of kirkstone branch

microhobby commented 11 months ago

@leonheldattoradex could you please share the command that you used to rebase the work here? I'm not sure, but I think that the commits from the common should stay on top 🤔

leonheldattoradex commented 11 months ago

I'm not sure, but I think that the commits from the common should stay on top 🤔

They are... the stupid GitHub interface ranks the commits in reverse order.

Anyway, this also confused me, it's clear now. I'll update the manifest based on c38cbc8f003f7f52f9397d0637d252b279bf2a98.