Re: {bb} hpjd.sh tests turn purple after installing bbgen

[Philip Clark <bblist@cannae.uklinux.net>]

On Sat, 2005-09-17 at 00:11, Brookins, Neil (YBUSA-KOP) wrote:
> I installed bbgen and all my tests via hpjd.sh (from www.deadcat.net)
> went purple.
> 
> I figured out what happened. It turns out that hpjd.sh is not invoked
> from bb-bbexttab like most ext scripts, but is actually invoked from
> bb-network.sh which was replaced when bbgen was installed.
> 
> The fix that I came up with was to insert this line into the new
> bb-network.sh file that comes with bbgen:
> 
> ---------------------------------------------------------------------
> bbhostgrep hpjd | awk '{ print "'$BBHOME'/ext/hpjd.sh " $1 " " $2 }' |
> sh
> ---------------------------------------------------------------------
> 
> Now, all my hpjd tests are green and are updating automatically again.
> 
> Is there a cleaner and/or shorter way to do this? Is anyone else using
> the hpjd external script with bbgen?

I think "cleanliness" is mostly a matte of personal preference, but
I don't think you'll find a shorter way to accomplish this. The
options that occur to me are:

  1. Hack on bbtest-net.c to get it to call hpjd.sh for the
     specified hosts. This is probably unwise.

  2. Modify hpjd.sh to parse the bb-hosts file and test each
     host in turn. This should be quite straightforward using
     bbhostgrep and would then allow you to simply call the
     script once from bb-bbexttab.

  3. Modify hpjd.sh to parse a separate config file to find
     which hosts to test and then call it from bb-bbexttab.

I'd opt for the third one, because I like to keep a clear
distinction between core BB test and externals. But that's
just me :)

Cheers, Phil.



-- 
Grabel's Law: 2 is not equal to 3 -- not even for large values of 2.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.