[Buildroot] Buildroot maintainer and stable releases
Nigel Kukard
nkukard at lbsd.net
Wed Jan 7 08:31:31 UTC 2009
> Ulf> You have complained about size of patches, and
> Ulf> that is why there is a prepatched toolchain for AVR32.
> Ulf> If that is not considered to be OK, then the several
> Ulf> MBytes of patches has to be introduced into the trunk.
> >>
> >> It's not the size in bytes as such, it's the special casing and
> >> (effectively) black box patches. Even when you test your changes on
> >> multiple archs there's a fairly big change that you break stuff for
> >> avr32/at91, or that you guys break it for the other archs. The same
> >> with moving packages to new versions or removing old versions, you
> >> cannot expect other people to forward port those arch specific
> >> patches.
>
> Markus> Yes, mplayer for example is more than 2 years old and includes a huge
> Markus> avr32 patch.
>
> Exactly. Who will redo this patch if I bump the mplayer version
Perfect example why we need the MAINTAINERS file, ie. who is responsible
for keeping the $arch/target patches up to date?
-N
More information about the buildroot
mailing list