[SeaBIOS] great things are coming your way :-)

[Peter Stuge]

ron minnich wrote:
> I don't even know what to say :-)
> 
>     Checking out SeaBIOS revision 51755c3b5ed9dcdfdef8cee56631d68642bde416
> Already on 'master'
> fatal: reference is not a tree: 51755c3b5ed9dcdfdef8cee56631d68642bde416

Sorry for not testing more thoroughly, the checkout did work for me,
I didn't expect the "regression" caused by:

commit eb129bbcb654d90c331b7898222d64f769c08437
Author: Patrick Georgi <patrick at georgi-clan.de>
Date:   Wed May 9 21:07:17 2012 +0200

    Update SeaBIOS URL
    
    We have a http accessible SeaBIOS mirror at review.coreboot.org.
    Use it.


Apparently our http accessible SeaBIOS mirror isn't getting updated,
so the SeaBIOS 1.7.1 release does not exist in what gets cloned.

If the above commit is reverted:

git revert eb129bbcb654d90c331b7898222d64f769c08437

..and the build/seabios directory is deleted, then the build will
work again. I am not sure that this is the right fix however.
I would prefer to have a reliable HTTP URL rather than reverting.


Here is an nginx snippet that allows to serve git http: from the
same virtual host as a gitweb:

location ~* ^/[^/]*\.git {
        alias /usr/libexec/git-core/git-http-backend;
        include /etc/nginx/fastcgi_params;
        fastcgi_param DOCUMENT_ROOT /var/lib/git;
        fastcgi_param GIT_PROJECT_ROOT /var/lib/git;
        fastcgi_pass
        unix:/var/run/spawn-fcgi/git-http;
}


And here's the fcgiwrap start script, to create that FastCGI socket.
All goes on one line of course.

#!/bin/sh
exec spawn-fcgi -n -s /var/run/spawn-fcgi/git-http -u gitweb -U nginx
-d /var/lib/git -f /usr/bin/fcgiwrap


Maybe it can help make direct HTTP access available for the actual
repository. Please let's not mess with mirroring. If nginx+fastcgi
does not fit the current hosting then I guess it will be Apache or
lighttpd, in which case the interwebs should have some snippets
equivalent to the above.


//Peter