[oe] [meta-openwrt] PV for git versions for 17.01.4 upstream release, git for master?

[Daniel F. Dickinson]

On 21/01/18 11:53 PM, Khem Raj wrote:
> On Sun, Jan 21, 2018 at 6:06 PM, Daniel F. Dickinson
> <cshored at thecshore.com> wrote:
>> Hi,
>>
>> Wondering thoughts on using a package version with the git revisions of
>> openwrt recipes that are in current stable (17.01.4) and using _git version
>> for tracking upstream master?  Also in that case would it be necessary to
>> use PREFERRED_VERSION for in e.g. openwrt.bbclass, or it a versioned recipe
>> preferred to a git one, unless overridden?
>>
> 
> Probably weakly define a global openwrt version e.g. OPENWRT_VERSION
> in layer.conf
> have two versions of recipes one for master and another one for
> release. OPENWRT_VERSION
> then can be overridden in local.conf if someone does not want to use
> release version.
> defining PREFERRED_VERSION for every recipe in layer.conf in meta-openwrt.
> 
>> Openwrt doesn't cut tarball releases of the sources that I am aware of, and
>> only some of the code is on github; there's a lot at git.openwrt.org.
>>
>> (Oh and for those not in the loop, Openwrt and LEDE have re-merged; for
>> those really not in the loop Openwrt was forked into LEDE project for
>> a while).
>> --
>> https://www.thecshore.com

Are there some examples of this kind of thing I could look at?  I'm not 
terribly familiar with OpenEmbedded yet (enough to do some work, but 
still lots to learn).

Regards,

Daniel

--
https://www.thecshore.com