[LEDE-DEV] Release 17.01.0 binary packages have changed and SDK inconsistency
Pau
pau at dabax.net
Wed Mar 29 09:11:48 PDT 2017
On 29/03/17 09:16, Alberto Bursi wrote:
>
>
> On 03/29/2017 02:45 AM, Daniel Golle wrote:
>> I get that problem, and it can be solved easily by removing the git
>> commit hash from feeds.conf in the SDK and rather use the current
>> snapshot instead.
>> I agree that the lack of a lede-17.01 release branch on the package
>> feeds may cause weird and problematic situations, especially in the
>> future once LEDE HEAD has diverged more from 17.01.x released versions.
>>
>
> Wat? Package feeds all have a branch for LEDE 17.01.
>
> https://github.com/openwrt-routing/packages/tree/lede-17.01
> https://github.com/openwrt/telephony/tree/lede-17.01
> https://github.com/openwrt/luci/tree/lede-17.01
> https://github.com/openwrt/packages/tree/lede-17.01
>
> Why is the SDK not using that and is targeting commits instead?
>
+1 to that question.
If the idea is to have a "moving release" instead of a "snapshot
release" why the SDK feeds are pointing to static commits and TAGS and
not to branches?
> -Alberto
>
> _______________________________________________
> Lede-dev mailing list
> Lede-dev at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev
>
--
./p4u
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/lede-dev/attachments/20170329/f55a3446/attachment-0001.sig>
More information about the Lede-dev
mailing list