[Buildroot] [PATCH] odroid-mali: mark package as BROKEN

daggs daggs at gmx.com
Wed Mar 8 06:55:14 UTC 2017


Greetings,

>
> Hello,
> 
> On Tue, 7 Mar 2017 18:05:02 +0100, Arnout Vandecappelle wrote:
> 
> >  The problem with BROKEN is the same as with BR2_LEGACY: it doesn't appear in
> > the legacy menu. You could argue that BROKEN is different because it simply
> > can't be used at all. However, for the user there is no difference: it used to
> > work (I hope we can assume that when a package is added, it has worked at least
> > once on at least one platform...), and after a Buildroot update it suddenly
> > vanishes.
> 
> Agreed. In this specific case, I believe odroid-mali definitely works
> for some situations, so there are certainly valid use cases for the
> package as it is today, i.e it is not *completely* broken. But it
> causes some build failures, which nobody has taken care of, and
> upstream is unlikely to be responsive/
> 
> >  So I propose the following: we can still mark things as BROKEN as a way to
> > motivate people to fix them, but during the RC month we properly remove them and
> > add a legacy entry.
> 
> Full ACK.
> 
> Thomas

my apologies, I've missed the initial mail with all the mails I'm getting.
I have a more direct line of communication to upstream, I'll try contacting them. will update asap.

as there is no x11 driver for this board (still pending review, not that it matters now), the usage of this pkg is rather limited.
the main usage is to run kodi, afaik kodi doesn't depends on libepoxy, so depending the pkg on kodi for now might be a valid solution.
I have fairly recent img (built 2 weeks ago based on the synced kodi 17 branch) and it compiled well without any errors.

thoughts?

DAgg.



More information about the buildroot mailing list