Re: [RFC] Setting default IMAGE_FSTYPES to tar.gz in bitbake.conf

["Mike (mwester)" <mwester@dls.net>]

Paul Sokolovsky wrote:
> Hello,
>
> On Sat, 09 Feb 2008 18:55:33 +0000
> Richard Purdie <rpurdie@rpsys.net> wrote:
>
> []
>
>   
>> The DISTRO can override the machine if it wishes now with no change to
>> OE, that is up to the distros concerned. That doesn't stop machines
>> from having sane defaults.
>>
>>     
>>> Well, as usual, thoughts aloud. I'm going to add 
>>> IMAGE_FSTYPES ?= "jffs2" to the machines from your 1st list to get
>>> matter going.
>>>       
>> ok.
>>
>>     
>
> Done, so are we ready for this patch now?
>
>
> @@ -541,7 +545,7 @@ DL_DIR ?= "${TMPDIR}/downloads" 
>  ################################################################## 
>   
>  DL_DIR ?= "${TMPDIR}/downloads" 
> -IMAGE_FSTYPES ?= "jffs2" 
> +IMAGE_FSTYPES ?= "tar.gz" 
>   
Why exactly are we simply replacing a jffs2 default with a new default?  
Just to make some other parties happier?  Wouldn't it be simply better, 
if this is such a big deal, to do:

+IMAGE_FSTYPES ?= "you-must-define-an-image-fstype-that-is-suitable-for-you"

That way we ensure that *nobody* relies on defaults, and everything is 
correctly defined in every case, and if someone fails to define it, it 
should be pretty obvious what they did wrong.

>  PCMCIA_MANAGER ?= "pcmcia-cs" 
>  DEFAULT_TASK_PROVIDER ?= "task-base" 
>  MACHINE_TASK_PROVIDER ?= "${DEFAULT_TASK_PROVIDER}" 
>
>
>   
>> Cheers,
>>
>> Richard
>>     
> Mike (mwester)
>
>
>