search

OpenXT / openxt

Base OpenXT build scripts
48 stars 39 forks source link

Jethro merge #89

Closed aikidokatech closed 8 years ago

aikidokatech commented 8 years ago

These changes are for building the xenclient-oe repo against the current OE Jethro (2.0) release. Make sure to use a new or updated build host/container. See https://openxt.atlassian.net/wiki/display/BS/Jessie+systemd+container for instructions on creating a new Jessie systemd container.

rossphilipson commented 8 years ago

I agree with @jean-edouard about this. I don't see why we would do pulls on the OE repos after the setupoe step has been run the first time. It seems it would be better for the setupoe step to see it had run and just exit.

aikidokatech commented 8 years ago

An OE branch is not frozen once created. It receives bug fixes and security updates. The goal of this work is to simplify the updating of the repos to pull in the latest patches. If removed one will need to manually update the repos. On Feb 2, 2016 11:40 AM, "Ross Philipson" notifications@github.com wrote:

I agree with @jean-edouard https://github.com/jean-edouard about this. I don't see why we would do pulls on the OE repos after the setupoe step has been run the first time. It seems it would be better for the setupoe step to see it had run and just exit.

— Reply to this email directly or view it on GitHub https://github.com/OpenXT/openxt/pull/89#issuecomment-178749287.

jean-edouard commented 8 years ago

@aikidokatech for some repos we checkout a specific commit ID, which pretty much means we don't want auto-updates.

Now regarding the OE branch, that's a very important topic, as including the tip of a moving branch breaks build reproducibility. Now maybe it's ok for master follow the tip of the OE jethro branch, and stable-X to build against a specific commit ID? master builds wouldn't be reproducible, but stable-X ones would... Maybe that's a discussion for the mailing list?

aikidokatech commented 8 years ago

Correct, meta-java will be an exception for now. There are no other repos that use a specific hash.

I disagree about the other repos. The updates they receive should typically not break a build as the branches are intended to be stable once released. Discussing this on the list would get better visibility. On Feb 2, 2016 12:24 PM, "Jed" notifications@github.com wrote:

@aikidokatech https://github.com/aikidokatech for some repos we checkout a specific commit ID, which pretty much means we don't want auto-updates.

Now regarding the OE branch, that's a very important topic, as including the tip of a moving branch breaks build reproducibility. Now maybe it's ok for master follow the tip of the OE jethro branch, and stable-X to build against a specific commit ID? master builds wouldn't be reproducible, but stable-X ones would... Maybe that's a discussion for the mailing list?

— Reply to this email directly or view it on GitHub https://github.com/OpenXT/openxt/pull/89#issuecomment-178771308.