Re: Strange file names

[Detlev Zundel <dzu@denx.de>]

Hi Tom,

thanks for listening to my concerns.  I have to admit though, that I
wrote my mail because of my doubts about the usage of such unusal
filenames, but I have yet to understand how you use the constructs.

> Yes, I think it would make sense for various reasons to get rid of it if
> possible - it's not central to the mechanism, just convenient.
>
> So the current uses of it are the following:
>
> - having a particular filename match the machine name:
>  
>     ./powerpc/conf/machine/{{=machine}}.conf

Can you explain to me what this exactly does?  Does that file match
every machine name?  If that is the case, then why do you need to match
at all and not use a special file name?

> - having a particular filename conditionally included or not:
>
>     ./i386/recipes-kernel/linux/{{ if kernel_choice ==
> "linux-yocto_3.2": }} linux-yocto_3.2.bbappend
>
> For those two types of cases, I think it should be possible to move that
> logic into the file itself using special filename and/or conditional
> filename directives.

I'm not sure if I understand fully, but something like (shell-syntax)
"include ${kernel_choice}.bbappend" would work - modulo ignoring errors
if the file is not found of course.

> The other usage is to have directory names match the machine name for
> instance:
>
>  ./i386/recipes-graphics/xorg-xserver/xserver-xf86-config/{{=machine}}/{{ if xserver_choice == "xserver_vesa": }} xorg.conf

I fail to understand this for the same reason than the first item ;)

Cheers
  Detlev

--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de