On Wed, Feb 25, 2004 at 11:08:59AM -0700, Tom Rini wrote:
> I can understand that.  How about:
> for board in arch/$(ARCH)/configs/*defconfig; \
>  do \
>    if [ -f $board ]; then
>     ...
>    fi
>  done
> 
Simply just matching on *defconfig should be fine. I already changed this on
matching defconfig-* for sh to get around matching SCCS.

> > Also the "- Build for xxxxx" is not good enough.
> 
> Erm, it's usually something descriptive enough, if one is firmiliar with
> the platform / what's intended to build.
> 
> > I will try to come up with a patch the uses a file named
> > arch/$(ARCH)/configs/index.txt
> 
> The 'issue' with configs/index.txt, I'll wager, is that for every new
> board, that's one more file to modify (and thus possibly conflict on).
> 
Agreed. The whole reason I did the automated "- Build for foo" thing is that
it's completely automated, and people building should already know what their
target is (if not, they can look at arch/$(ARCH)/Kconfig and figure it out).
I suppose it's not particularly descriptive, but it seems more sensible to
have an abbreviated help text then none whatsoever.