[Buildroot] How handle broken or partly broken packages in the distribution

Hans-Christian Egtvedt hans-christian.egtvedt at atmel.com
Mon Jan 26 06:05:45 UTC 2009

On Fri, 23 Jan 2009 15:12:56 -0200
Thiago A. Corrêa <thiago.correa at gmail.com> wrote:

> On Fri, Jan 23, 2009 at 6:57 AM, Hans-Christian Egtvedt
> <hans-christian.egtvedt at atmel.com> wrote:
> >> so they are not selectable for AVR32 users
> >>
> >
> > To make it harder to fix the problem with the packages?
> >
> > It might also be a result from the development environment on your
> > build machine, like the recent alsa-utils errors somebody else
> > found on opensuse, which I have not triggered in my Ubuntu system.
> >
> I agree with HCE. Making packages unselectable or invisible is not a
> good approach.
> I think it would be very sufficient to just document it on the help
> string and take it out of the defconfig for that arch.

Or just have a Wiki with a list of all packages and which archs they
work and do not work on. Users should also see/find this table fast, so
they easily know what is expected to work and what is not.

It might even encourage users to start fiddling with packages not

Best regards,
Hans-Christian Egtvedt

More information about the buildroot mailing list