<feed xmlns='http://www.w3.org/2005/Atom'>
<title>staging/chunkeey/scripts/metadata.pm, branch v19.07.3</title>
<subtitle>Staging tree of Christian Lamparter</subtitle>
<id>https://git.openwrt.org/openwrt/staging/chunkeey/atom?h=v19.07.3</id>
<link rel='self' href='https://git.openwrt.org/openwrt/staging/chunkeey/atom?h=v19.07.3'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/'/>
<updated>2019-09-04T11:39:37Z</updated>
<entry>
<title>build: allow overriding default selection state for devices</title>
<updated>2019-09-04T11:39:37Z</updated>
<author>
<name>Jonas Gorski</name>
</author>
<published>2019-08-13T10:33:47Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=f783ad5b5b105407fd47123b02217a8a09525b44'/>
<id>urn:sha1:f783ad5b5b105407fd47123b02217a8a09525b44</id>
<content type='text'>
Allow overriding the default selection state for Devices, similar to
setting a default for packages.

E.g. by setting DEFAULT to n, they won't be selected by default anymore
when enabling all device in the multi device profile.

This allows preventing images being built by the default config for
known broken devices, devices without enough RAM/flash, or devices not
working with a certain kernel versions.

This does not prevent the devices from being manually selected or images
being built by the ImageBuilder. These devices often still have worth
with a reduced package-set, or as a device for regression testing, when
no better device is available.

Signed-off-by: Jonas Gorski &lt;jonas.gorski@gmail.com&gt;
(cherry picked from commit 7546be60074e452751ba2a48eddbc13910bec708)
</content>
</entry>
<entry>
<title>build: add a config option for enabling a testing version of the target kernel</title>
<updated>2019-05-11T09:37:10Z</updated>
<author>
<name>Felix Fietkau</name>
</author>
<published>2019-04-27T17:13:07Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=85017c40f4efce11edd77e0caac14aed0fd690eb'/>
<id>urn:sha1:85017c40f4efce11edd77e0caac14aed0fd690eb</id>
<content type='text'>
If the target supports a newer kernel version that is not used by default
yet, it can be enabled with this option

Signed-off-by: Felix Fietkau &lt;nbd@nbd.name&gt;
</content>
</entry>
<entry>
<title>IB: include SUPPORTED_DEVICES in 'make info' output</title>
<updated>2019-03-11T04:32:29Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2019-03-11T04:32:29Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=d6fa04a437033d4bdfa1b0d90a4786bfe492f749'/>
<id>urn:sha1:d6fa04a437033d4bdfa1b0d90a4786bfe492f749</id>
<content type='text'>
Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
<entry>
<title>ib: display whether profile comes with image metadata</title>
<updated>2019-03-06T13:50:42Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2019-03-06T13:45:15Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=13c379e5c6e37b3822bf6e4e18cc6317e5b40fbb'/>
<id>urn:sha1:13c379e5c6e37b3822bf6e4e18cc6317e5b40fbb</id>
<content type='text'>
Having image metadata (and signature) appended is a condition for
semi-automated sysupgrade, hence IB needs to be able to tell which
images will end up with metadata.

Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
<entry>
<title>build: expose ABI version in .packageauxvars</title>
<updated>2019-01-19T13:32:01Z</updated>
<author>
<name>Jo-Philipp Wich</name>
</author>
<published>2019-01-18T11:43:06Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=e3d5b384aa67c5562d59e8745fc6c48a9f2a997d'/>
<id>urn:sha1:e3d5b384aa67c5562d59e8745fc6c48a9f2a997d</id>
<content type='text'>
Subdequent commits need this information to resolve the ABI version when
computing binary ipk dependencies.

Signed-off-by: Jo-Philipp Wich &lt;jo@mein.io&gt;
</content>
</entry>
<entry>
<title>scripts/metadata.pm: avoid adding dup names in provides list</title>
<updated>2018-09-09T01:21:01Z</updated>
<author>
<name>Yousong Zhou</name>
</author>
<published>2018-09-05T15:29:25Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=204081670b914795a494929777f09807b15f70f4'/>
<id>urn:sha1:204081670b914795a494929777f09807b15f70f4</id>
<content type='text'>
The need arises from building Open vSwitch kernel datapath modules, e.g.

 - kmod-openvswitch from Linux upstream
 - kmod-openvswitch-intree from openvswitch source code

where both provides virtual package "kmod-openvswitch" for userspace
packages to select and depend on

Signed-off-by: Yousong Zhou &lt;yszhou4tech@gmail.com&gt;
</content>
</entry>
<entry>
<title>scripts/metadata.pm: allow group-only Require-User specs</title>
<updated>2018-02-26T06:19:46Z</updated>
<author>
<name>Matthias Schiffer</name>
</author>
<published>2018-02-26T06:10:32Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=884c9575e1c6ac4f53a313c99f3e65a2efa77bd1'/>
<id>urn:sha1:884c9575e1c6ac4f53a313c99f3e65a2efa77bd1</id>
<content type='text'>
/lib/functions.sh can deal with Require-User specifications that only
contain a group, but no user. Adjust metadata.pm to allow such
specifications as well.

Signed-off-by: Matthias Schiffer &lt;mschiffer@universe-factory.net&gt;
</content>
</entry>
<entry>
<title>build: remove obsolete "package feature" feature</title>
<updated>2018-01-13T18:54:45Z</updated>
<author>
<name>Matthias Schiffer</name>
</author>
<published>2018-01-08T11:31:03Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=4bb54ed15ee4647c36a4c2b3cb9416f344594b8a'/>
<id>urn:sha1:4bb54ed15ee4647c36a4c2b3cb9416f344594b8a</id>
<content type='text'>
Package "features" seem to be unused for some time. In any case, custom
Config.in snippets and package PROVIDES are a much more flexible way to
express similar options.

Signed-off-by: Matthias Schiffer &lt;mschiffer@universe-factory.net&gt;
</content>
</entry>
<entry>
<title>metadata: scripts/feeds: distinguish between source and binary packages, resolve virtual dependencies</title>
<updated>2018-01-13T18:54:45Z</updated>
<author>
<name>Matthias Schiffer</name>
</author>
<published>2018-01-11T17:38:42Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=52719c2b67aff4b406e23ea5ed746c6c006e85bc'/>
<id>urn:sha1:52719c2b67aff4b406e23ea5ed746c6c006e85bc</id>
<content type='text'>
Properly resolve build depends to source packages and runtime depends to
binary packages. Dependencies on virtual packages are resolved to the first
provider now.

Signed-off-by: Matthias Schiffer &lt;mschiffer@universe-factory.net&gt;
</content>
</entry>
<entry>
<title>metadata: always resolve dependencies through provides list</title>
<updated>2018-01-13T18:54:44Z</updated>
<author>
<name>Matthias Schiffer</name>
</author>
<published>2018-01-08T11:17:30Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=47d6b05ad328e80e4ee05e48aa95462f3518c014'/>
<id>urn:sha1:47d6b05ad328e80e4ee05e48aa95462f3518c014</id>
<content type='text'>
Instead of adding virtual packages to the normal package list, keep a
separate list for provides, make each package provide itself, and resolve
all dependencies through this list. This allows to use PROVIDES to replace
existing packages.

Fixes FS#837.

Signed-off-by: Matthias Schiffer &lt;mschiffer@universe-factory.net&gt;
</content>
</entry>
</feed>
