Re: gnu/system/u-boot.scm

[ludo@gnu.org (Ludovic Courtès)]

Hi Danny,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> On Tue, 26 Jul 2016 22:49:35 +0200
> ludo@gnu.org (Ludovic Courtès) wrote:
>
>> >   (u-boot          u-boot-configuration-u-boot           ; package
>> >                    (default (@ (gnu packages u-boot) (make-u-boot-package board))))  
>> 
>> The default value has invalid syntax.  Should be simply:
>> 
>>   (default (make-u-boot-package board))
>> 
>> but I think this doesn’t work (‘board’ will be unbound; yeah,
>> counter-intuitive.)
>> 
>> You could instead do (default #f) and call ‘make-u-boot-package’ when
>> that value is #f.
>> 
>> > (define (eye-candy config root-fs system port)
>> >   "dummy"
>> >   (mlet* %store-monad ((image #f))
>> >     (return (and image
>> >                  #~(format #$port "")))))
>> >  
>> 
>> Simply remove it.  :-)
>
> Yeah, but there's a 
>
>   (mlet %store-monad ((sugar (eye-candy config store-fs system #~port)))
>
> in the same file.
>
> Can I remove that and #$sugar , too? Will it still work?

Yes.

> Also, I'm trying to s/grub.cfg/bootloader-configuration-file/g right now, but I wonder
>
> (1) Whether it's possible to determine the basename of the config-file derivation in order to find out what bootloader to install
> (2) Whether we want to do it that way
>
> .
>
> If so, we could have a install-bootloader routine that detects what the filename of the bootloader-configuration-file object is and then calls either install-grub or install-u-boot.

I think we need two separate procedures on the build side:
‘install-grub’, and ‘install-u-boot’.

Choosing between GRUB and U-Boot should happen on the “host side”,
mostly likely in (gnu system).

HTH,
Ludo’.