<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-updater.git/conf/distro/sota.conf.inc, branch dev/nxp</title>
<subtitle>Mirror of github.com/advancedtelematic/meta-updater</subtitle>
<id>https://git.enea.com/cgit/linux/meta-updater.git/atom?h=dev%2Fnxp</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-updater.git/atom?h=dev%2Fnxp'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/'/>
<updated>2020-02-28T12:42:02+00:00</updated>
<entry>
<title>meta: move HOSTTOOLS definitions to sota.conf.inc</title>
<updated>2020-02-28T12:42:02+00:00</updated>
<author>
<name>Ming Liu</name>
<email>liu.ming50@gmail.com</email>
</author>
<published>2020-01-26T21:14:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=b736c8524b85f3e2d3e21fd77c4b5587316b665f'/>
<id>urn:sha1:b736c8524b85f3e2d3e21fd77c4b5587316b665f</id>
<content type='text'>
HOSTTOOLS and HOSTTOOLS_NONFATAL are global variables that being
handled in base_eventhandler, so they must be defined in config files
or in INHERIT classes or classes being inherited by base.bbclass, or
else we might run into the following problems:
```
$ bitbake pkgname
$ bitbake imgname
```

the HOSTTOOLS and HOSTTOOLS_NONFATAL in the above image recipe, for
instance, 'repo python' in image_repo_manifest.bbclass, they would not
be copied to HOSTTOOLS_DIR.

Signed-off-by: Ming Liu &lt;liu.ming50@gmail.com&gt;
</content>
</entry>
<entry>
<title>sota.conf: use reproducible builds by default</title>
<updated>2019-01-29T16:02:31+00:00</updated>
<author>
<name>Stefan Agner</name>
<email>stefan.agner@toradex.com</email>
</author>
<published>2019-01-29T16:02:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=3d3a0bf9faff855bb4bc0b17611036d3cfbc7ff9'/>
<id>urn:sha1:3d3a0bf9faff855bb4bc0b17611036d3cfbc7ff9</id>
<content type='text'>
Use reproducible builds by default. OSTree sets mtime to 0 at
commit time anyway. This makes sure that all mtime timestamps
are 0 already at build time. This is relevant for programs
which relies on mtime of deployed artifacts at runtime.

Python for instance writes the mtime of the source file into
bytecode files (pyc) at build time. When OSTree then clears
the mtime Python considers all bytecode files as stale.

Reproducible binaries also avoid unnecessary differences
between two OSTree commits. E.g. if the sstate cache is
cleared between two OSTree commits OpenEmbedded might create
slightly different binaries.

Note however that not all all recipe generate reproducible
binaries at this time.

Signed-off-by: Stefan Agner &lt;stefan.agner@toradex.com&gt;
</content>
</entry>
<entry>
<title>sota.conf: use usrmerge</title>
<updated>2018-11-28T15:30:23+00:00</updated>
<author>
<name>Stefan Agner</name>
<email>stefan.agner@toradex.com</email>
</author>
<published>2018-11-28T15:23:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=8f08a3b489206a2137600941eb45198cf15cecc9'/>
<id>urn:sha1:8f08a3b489206a2137600941eb45198cf15cecc9</id>
<content type='text'>
OSTree needs UsrMove to be implemented, meaning that everything
should be in /usr. OpenEmbedded has a distro feature usrmerge which
implements exactly that, and makes sure that no package install
anything in /bin, /sbin or /lib. Make use of it.

Signed-off-by: Stefan Agner &lt;stefan.agner@toradex.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'morty' into pyro</title>
<updated>2017-07-05T10:11:52+00:00</updated>
<author>
<name>Anton Gerasimov</name>
<email>anton@advancedtelematic.com</email>
</author>
<published>2017-07-05T10:11:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=69a0db9291725b1ddfa643dc00d6d2f1bf6c5caf'/>
<id>urn:sha1:69a0db9291725b1ddfa643dc00d6d2f1bf6c5caf</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix build issues with yocto pyro</title>
<updated>2017-07-04T14:08:15+00:00</updated>
<author>
<name>Anton Gerasimov</name>
<email>anton@advancedtelematic.com</email>
</author>
<published>2017-07-04T14:08:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=e39692a25858acf79fedf44b9d9fdd8e71337957'/>
<id>urn:sha1:e39692a25858acf79fedf44b9d9fdd8e71337957</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Set default SOTA_CLIENT directly in sota.bbclass</title>
<updated>2017-06-08T15:54:32+00:00</updated>
<author>
<name>Anton Gerasimov</name>
<email>anton@advancedtelematic.com</email>
</author>
<published>2017-06-08T15:54:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=08e225b8e66e25003108921c0b05688c7ea6892e'/>
<id>urn:sha1:08e225b8e66e25003108921c0b05688c7ea6892e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add option to choose which sota client to use (if any)</title>
<updated>2017-05-31T14:00:06+00:00</updated>
<author>
<name>Anton Gerasimov</name>
<email>anton@advancedtelematic.com</email>
</author>
<published>2017-05-31T10:36:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=20aae31c49333946ff83b009153d70763c8def8e'/>
<id>urn:sha1:20aae31c49333946ff83b009153d70763c8def8e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Extract common distro configuration into sota.conf.inc</title>
<updated>2017-05-23T13:51:06+00:00</updated>
<author>
<name>Phil Wise</name>
<email>phil@advancedtelematic.com</email>
</author>
<published>2017-05-23T12:17:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=a446bf18f0ef68a1a39fbf51d79cec2fa8bb4bf2'/>
<id>urn:sha1:a446bf18f0ef68a1a39fbf51d79cec2fa8bb4bf2</id>
<content type='text'>
Pull the common lines from the poky-sota.conf and poky-sota-systemd.conf
example distributions into a separate include file that can be pulled into
other environments.

This might be by including it in a user's own custom distro, or by directly
including it in local.conf (e.g. AGL).

  require conf/distro/sota.conf.inc
</content>
</entry>
<entry>
<title>Replace includes with bblcasses</title>
<updated>2017-04-26T09:04:39+00:00</updated>
<author>
<name>Anton Gerasimov</name>
<email>anton@advancedtelematic.com</email>
</author>
<published>2017-04-25T13:21:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=4d610e9f230dd23589b18588446c2368f3a99446'/>
<id>urn:sha1:4d610e9f230dd23589b18588446c2368f3a99446</id>
<content type='text'>
They are more flexible and allow tricks like conditionally inheriting
machine-related classes from the main one which makes things easier
for external users like AGL
</content>
</entry>
<entry>
<title>Move rvi-sota-client to poky-sota-systemd.conf</title>
<updated>2017-04-24T16:52:08+00:00</updated>
<author>
<name>Anton Gerasimov</name>
<email>anton@advancedtelematic.com</email>
</author>
<published>2017-04-24T16:52:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=f76663ba97b055a7a063221e4a7992330e692a3c'/>
<id>urn:sha1:f76663ba97b055a7a063221e4a7992330e692a3c</id>
<content type='text'>
</content>
</entry>
</feed>
